Skip to content

Conversation

@danolivo
Copy link
Contributor

By this we revise UI Spock functions and improve their documentation.

@danolivo danolivo self-assigned this Sep 26, 2025
location
(optional) Text string identifying the node location as precise as needed. Doesn't affect any internal logic.
country
(optional) Text string dedicated to conveniently store and expose the country code where the spock node is located. Doesn't affect any internal logic.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Text string dedicated to conveniently store and expose

should be

Text string dedicated to conveniently storing and exposing

Copy link
Member

@susan-pgedge susan-pgedge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good Andrei, just a couple of comments!

@danolivo danolivo force-pushed the docs-improvement-1 branch 2 times, most recently from b40a794 to 26fdf60 Compare October 1, 2025 13:08
@mason-sharp
Copy link
Member

I understand wanting to improve the parameter names, but I am hesitant to break anyone's scripts if they are using named parameters in calls such as select calc_something(quantity => 3, price => 2).

Can you please do a doc only PR, without any C file changes first?

- Add some internal details on what exactly the routine does.
- Each parameter is briefly explained
- The spock_country_code GUC is obsolete and removed.
- Minor changes caused by automatic trailing backspace removal
Some typo corrections in different places of the code are also included here.
…unctions.

Some minor typos and trailed whitespaces fixed here and there in the code.
Also, this commit commences restructurisation of the UI .sql script to make it
a little more readable and synced with the docs/spock_functions.md.
- Revert fixes of code style and typos in c-files.
@danolivo
Copy link
Contributor Author

I understand wanting to improve the parameter names, but I am hesitant to break anyone's scripts if they are using named parameters in calls such as select calc_something(quantity => 3, price => 2).

Can you please do a doc only PR, without any C file changes first?

Not sure about the reason, but done.

| spock.spock_version | Returns the Spock version in a major/minor version form: `4.0.10`.
| spock.spock_version_num | Returns the Spock version in a single numeric form: `40010`.
| spock.get_channel_stats | Returns tuple traffic statistics.
| spock.get_country | Returns the country code if explicitly set; returns `??` if not set.
Copy link
Member

@mason-sharp mason-sharp Oct 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confirmed with Asif, that we should NOT remove this. Thanks.

@danolivo

@pgEdge pgEdge deleted a comment from danolivo Nov 3, 2025
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

Successfully merging this pull request may close these issues.

4 participants