status field failed to properly filter returned data when specified in conjunction with the android or ios-strings formats.useDittoSingleText and useDittoComponent. These hooks are experimental and will likely undergo API changes in the future.status field to data returned from the /components and /projects/:id/components endpoints.PUT /components endpoint.\n, \t, @, ?, ', and " characters are now properly escaped.xliff namespace to exported Android .xml files..xml exports that occurred with text items with API IDs that include the - character. Now, all - characters are replaced with _ characters in the name property of <string> and <plural> tags, and a ditto_api_id property has been added to string and plural tags to serve as a reference to the original API ID.project add / project remove commands and selecting the component library caused incorrect modifications to be made to the CLI's configuration file.ditto-dir input parameter for projects that do not have the ditto directory in the root of the repositoryPUT /components.format query parameter can now accept values of android or ios-strings.GET /variables endpoint that returns the variables in the workspace of the requesting user.status query parameter in API requests. Supported by the following endpoints:GET /projectsGET /projects/:idGET /projects/:id/componentsGET /componentsmeta option flag in support of the Ditto GitHub Action releaseapp.dittowords.com (instead of the old beta.dittowords.com)DITTO_TEXT_DIRconfig.yml file an additional help message displays about verifying that the projects have developer mode enabledvariables prop.count prop. DITTO_API_KEY).pull command no longer crashes when projects other than the component library are specified in config.ymlproject add command that was causing it to crashditto/config.yml to allow explicitly specifying that the component library should be fetched and included in the CLI's output:GET /projects/:id/components can now be used to fetch the components used in a projectGET /components endpointformat and variant parameters (the same as the /projects, /project/:id, and /components endpoints)GET /components can now be used to fetch the components in a workspace format and variant parameters (the same as the /projects and /project/:id endpoints)GET /projects/ditto_component_library has been deprecated; the endpoint is still available, but references to it have been removed from the documentation.PUT /components can now be used to update the text of components in a workspacevariant query parameter (an error will be thrown if not specified)team or enterprise plansdata key in request body and must be in one of our three supported import formats: https://www.dittowords.com/docs/importing-string-jsonsvariants option is set and a format of structured or flat is specified, output files will be written on a per-project per-variant basisstructured and flat formats is saved without arbitrary top-level nestingditto-react now only works with CLI version 2.x.x — leaning into new CLI improvements allowed us to drastically reduce many areas of complex logical overheadframeId, blockId, textId, or componentId values are handledreact-i18next: https://github.com/dittowords/ditto-demo/tree/react-i18nextflat and structured JSON exports. Now, hidden text will correctly not be included in these export formats!pull command is executed, all .json and .js files are now removed from the ditto folder prior to new data being writtenditto/config.yml:variants: true or falsetrue, data will be fetched for both base and variant text and stored in separate JSON filesformat: flat or structuredGET /variants will now return names and API IDs for variants in the workspace associated with the requesting user.flat and structured formatsvariant value to DittoProviderditto-sdk usage to integrate with a component library instead of an individual projectditto-react and ditto-cli support for variants/projects usage in API Reference. The projectIds query parameter should be specified as follows:?projectIds[]=<PROJECT_ID>&projectIds[]=<PROJECT_ID>?projectIds[]=<PROJECT_ID>,<PROJECT_ID>GET /variants will now return names and API IDs for variants in the workspace associated with the requesting user.GET /projects and GET /projects/:id now accept an optional query parameter of variant; when provided, the data exported will be specific to the variant with an API ID that matches the parameter's value. For default and structured formats, the variants key will not be included when the variant parameter is provided./projects/<PROJECT_ID>?variant=xxx-xxx-xxxGET /projects/:id will not include top-level projects and project_xyz keysGET /projects/123{ projects: { project_123: { text_item: "Hello World", ... }}}{ text_item: "Hello World", ... }GET /projects and GET /projects/:id now accepts an optional query parameter of format, which can be either flat or structured. If no format is provided, the full JSON of the project will be returned with blocks and frames. /projects/<PROJECT_ID>?format=flatGET /projects/:id will now return component variants. This applies both for when fetching projects or when fetching the component library (i.e. id = ditto_component_library)GET /projects/:id will now match the project JSON export from the web-app to include component information (is_comp and component_api_id) in the text objecttext.json.projectId prop can be passed to DittoProvider or DittoDittoProvider, all descendant Ditto components will default to pulling text from the associated projectDitto, the component will pull text from the associated projectDittoProvider and Ditto, the value passed to Ditto will take precedenceDitto component is rendered that is not provided a projectId via direct prop or DittoContext ancestor, an error will be thrownditto-react to version 0.0.4 ditto-react version by passing projectId props to all instances of DittoContextGET /project-names is the new name of the previous GET /projects endpoint. Just as before, this will return the names and IDs of projects in your Ditto workspace with Developer Mode turned onGET /projects/:id will now return the structured JSON in a format compatible with multiple projectsGET /projects is a new endpoint that will return the content of multiple projects (specified via the query parameter projectIds) as a single JSON object /ditto/config.yml now supports multiple projects. ditto-cli pull will pull all projects in the current directory's /ditto/config.yml/ditto/config.ymlditto-cli project addditto-cli project remove ditto-cli project command will now function as ditto-cli project addGET /projects now includes the Component Library if Developer Mode is enabled for the Component LibraryGET /projects/:id will return the Component Library as a structured JSON if the ID provided is ditto_component_library GET /projects endpoint for fetching Ditto projects from workspaceGET /projects/:id endpoint for fetching content in Ditto project as structured JSON