Skip to content
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

suggestion, version number #7

Open
rwu2359 opened this issue May 17, 2017 · 2 comments
Open

suggestion, version number #7

rwu2359 opened this issue May 17, 2017 · 2 comments

Comments

@rwu2359
Copy link

rwu2359 commented May 17, 2017

suggestion
adding a version number script to the solution to help when there ar emultiple copies on your hard drive

@tjsoftworks
Copy link

I would like to suggest specifically that we establish a FileMaker Developer standard that the version is allow set as part of the creation process for functions - a local variable in each function is a $version=0.0.1 where the version number follows SemVer practice. Ideally, one should be able to do the following.... FUNCTION_NAME.version returns the semver version of the function .... perhaps the input of a flag like "VERSION" short currents normal calculation and instead returns the semver version storaged in the function.

Inside the function definition the calculation reads like this....

$semver = 0.0.1

Case( inputparameter="VERSION"; semver;
...
//The rest of the functions workings
...
//normal function return value
normal_return_value
)

Another approach is to use a globalvariable $$semver for the semver value for ALL functions and thus the version is "available" as soon as the function is called without having to return it specifically. Recursive functions and functions that call other function are of course problematic but....
I have used this practice for a number of years. Each function call returns a bunch of env parameters as a BLOB ( perhaps a json BLOB at this point in time is the right way ) as a global variable and one can inspect it at any time either as a script step or in the developer console.

SemVer information can be found at SemVer.org

@toddgeist
Copy link
Contributor

I am violently opposed to Global Variable Space pollution, so please not that :-)

I think if we wait a bit longer, this problem will take care of itself :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants