OpenRefine / OpenRefine/openrefine.org
null data type
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 142
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 9
Description
Hi. I found an issue on this page:
https://openrefine.org/docs/manual/exploring
In particular:
#############################################################################################################
The data types supported are:
string (one or more text characters)
number (one or more characters of numbers only)
boolean (values of “true” or “false”)
date (ISO-8601-compliant extended format with time in UTC: YYYY-MM-DDTHH:MM:SSZ)
OpenRefine recognizes two further data types as a result of its own processes:
error
null
#############################################################################################################
I think that "null" data type may be replaced by "undefined". Is it right?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Exploring documentation page at https://openrefine.org/docs/manual/exploring and review the listed data types, especially the entries for error and null. Confirm whether null should be called undefined in OpenRefine, then update the wording if that terminology is correct. Done means the page uses the accurate data-type name and remains consistent with the surrounding descriptions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100