-
Notifications
You must be signed in to change notification settings - Fork 182
hidden fields, schema and service fields #231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
jacalata
commented
Jun 18, 2022
- hidden fields
- schema, service fields
- doc updates
- publish action
Add docstrings and remove clutter. I also made some very tiny tweaks to some code for clarity.
* Prep for release of 0.6 * wordsmithing the changelog
#111) * Added the ability to create and modify fields, including aliases and calculated fields
Python itself made this the default in 3.4. This will cover anyone on 2.7 or 3.3 (https://bugs.python.org/issue17201)
We are using this script for all our Tableau content.
Updating copyright date
Travis (and everyone else) no longer supports python 3.3 - vimalloc/flask-jwt-extended#89
Update bootstrap to address xss vulnerability: https://snyk.io/vuln/npm:bootstrap
Update datasource model docs
including sample for usage demo
Simply added Tyler's fix from #145 Also edited one of the sample files to present the issue
add some pretty printing of field data
tweak the file so it covers the bug in #145
caught in bvt test
1. because it doesn't drop unused namespaces the way ElementTree does 2. it isn't as vulnerable to bomb attacks
* create new publish-to-pypi action * delete travis jobs
* create new publish-to-pypi action * delete travis jobs
* add sample usage
Thanks for the contribution! Before we can merge this, we need @benlower @r-richmond @doulam @graysonarts @KernpunktAnalytics @jdomingu to sign the Salesforce.com Contributor License Agreement. |
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Kevin Glinski <k***@i***.com> Russell Hay <R***@U***.n***.g***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce.com Contributor License Agreement and this Pull Request will be revalidated. |
ignoring SLA complaints about lots of users, not sure why it wouldn't recognize Russell/Ben/etc from other repos? |