primordic/IssueDupesLite huggingface dataset:
Repository: bbatsov/projectile

Issue #171: When visiting file ignored in .projectile, it is still added to project cache
Created: 2013-11-02T20:39:54Z
I store thumbnails for image-dired in ~/.emacs.d/image-dired/. I've added /image-dired to .projectile that is in ~/.emacs.d/. The files are ignored from search, but if I visit some of them, they are cached. This is unexpected.

Duplicate issue #172: Add an option to purge files/subtrees from cache
Created: 2013-11-02T20:41:12Z
When I remove a file that is cached, projectile still thinks it exists. Currently, I need to invalidate the entire cache and build it anew, which is slow. It would be nice to be able to remove a specific file or subtree from the cache.

Closing comment (2013-11-02T20:51:10Z): Thanks. As you migh've guessed this is related to #171 . Since I have the entire ~/emacs.d/ stored as a project (and I have all my emacs developement/packages there), it's really big database to rebuild after every change.
Repository: bbatsov/projectile

Issue #1270: projectile-compile-project
Created: 2018-08-18T15:21:58Z
Not sure what's changed with this function, but I used to be able to set the compile command for the project's root. Now when I run it I get this:
The value for: compilation-dir in project-type: cmake was neither a function nor a string
Projectile Version: 20180815.2057

Duplicate issue #1281: projectile-compile-project: user-error: The value for: compile-command in project-type: generic was neither a function nor a string.
Created: 2018-09-13T09:28:36Z
Expected behavior
No error, the prompt for the compilation command should appear.
Actual behavior
user-error: The value for: compile-command in project-type: generic was neither a function nor a string.
Steps to reproduce the problem
It seems to be related to my project. Some are workings, other are failing like described above.
There is certainly a way to reset some cache associated with each project that would lead to this error message?
Environment & Version information
Projectile version information
Projectile 20180824.2239

Emacs version
25.1.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11)

0.200.13@25.1.1 (spacemacs)

Operating system
Debian GNU/Linux 9

Closing comment (2018-09-18T19:32:58Z): Same as #1270 ?
Repository: bbatsov/projectile

Issue #241: projectile-remember-window-configs usability problem
Created: 2014-01-05T20:44:27Z
I think I found a usability problem with this (nice) new feature: if you C-c p s and select some project, then C-c p s to another project and kill all the buffers of the first project, and then try to come back to the previous project it doesn't reopen the killed files. As a result, any of the usual commands like C-c p f just stays in the previous project, even tho you explicitely asked to switch to the other project before.
I'm not sure what the perfect solution would be, but here are some ideas:

reopen closed buffers if they were killed when switching. That is, always try to reopen the files and assign them to the correct windows.
run projectile-switch-project-action if no buffers from the project are found when switching.

I'd like 1) because it'd allow me to just kill all buffers from time to time, and still have it behave in a "DWIM" way when switching projects... one could also imagine to save/restore those configurations when quitting/loading emacs.
That said, 2) is probably much simpler to implement.

Duplicate issue #312: `projectile-switch-project` does nothing
Created: 2014-04-14T16:35:38Z
When I invoke projectile-switch-project, after selecting the project, it often (but not always) just returns me to the current buffer, with no explanation why.

Closing comment (2014-05-21T07:52:57Z): @bbatsov: none for me, as I said I don't use the feature anymore because it only solves half of my problems. One day I'll probably try to implement something and finally understand why all the other packages failed to do so :)
By the way, this is likely simply a duplicate of #241 as I mentionned.
Repository: bbatsov/projectile

Issue #633: Presence of .projectile file breaks getting the list of files
Created: 2015-02-03T07:21:26Z
As @bbatsov said, things worked before 5e46193

Duplicate issue #629: projectile-find-file-in-directory seems broken
Created: 2015-02-02T11:27:18Z
Here's the contents of my emacs.candidate project and directory with themes subdirectory:

Here're the candidates I get from projectile-find-file-in-directory when choosing themes directory (same for any other directory):

I don't actually know what the command intended behaviour is, but it's unlikely to be that. I'm using helm for completions but switching to ido doesn't make a difference. I'm using a fork of
origin (https://github.com/bbatsov/projectile.git):
          origin/HEAD -> master
7335b48   origin/gh-pages
74afdbb   origin/master

which has a couple of my local commits but those are only for perspective support and don't touch anything else.

Closing comment (2015-02-03T09:15:10Z): Might be related to #633.
Repository: bbatsov/projectile

Issue #1854: Adding a .projectile file causes "projectile-invalidate-cache: Wrong type argument: hash-table-p, nil"
Created: 2023-08-01T10:17:54Z
Expected behavior
Adding a .projectile file to the root of a project should not stop projectile-find-file from working.
Actual behavior
Adding a .projectile file (either empty or containing excluded directories) to the root of a project causes projectile-find-file to fail with "Wrong type argument: hash-table-p, nil"
Steps to reproduce the problem
Add a .projectile file
run projectile-find-file
Environment & Version information
Projectile version information
Projectile 2.7.0
Emacs version
Emacs 29.1.50, earlier also on Emacs 28
Operating system
Mac OS 12.6.7

Duplicate issue #1900: "Wrong type argument: hash-table-p, nil" when running projectile-find-file with enable-caching on
Created: 2024-08-23T12:57:42Z
Expected behavior
projectile-find-file works
Actual behavior
Wrong type argument: hash-table-p, nil printed in minibuffer
Steps to reproduce the problem
I have the following use-package setup:
(use-package projectile
  :bind-keymap ("C-c p" . projectile-command-map)
  :config (setq projectile-enable-caching t))
When I navigate to a project (git repo directory root) and enter C-c p f I get the error message.
Environment & Version information
Projectile version information
20240814.1854
Emacs version
GNU Emacs 30.0.60
Operating system
x86_64-apple-darwin23.5.0 (macOS Sonoma 14.6.1)

Closing comment (2025-01-26T03:12:55Z): This looks similar to #1854 and I do not have projectile-enable-caching enabled.
Repository: bbc/wraith

Issue #283: Default config domains no longer exists, which creates an error
Created: 2015-09-04T10:38:38Z
The default domains in the config from running wraith setup point to links that no longer exist:
# Add only 2 domains, key will act as a label
domains:
  arabic: "http://www.live.bbc.co.uk/arabic"
  russian: "http://www.live.bbc.co.uk/russian"
Replacing the links with anything else works perfectly well, although I can’t think of a good example of an Arabic and Russian BBC site with very similar designs to use instead.
I’ve tried to find whatever links they should have pointed to, but I’ve had no luck, which is why I’m filing this as an issue instead of a pull request. The sites also block crawlers, so archive.org is no use. (Great work all around by the Beeb.)

Duplicate issue #291: Default domains after wraith setup 404 in some countries
Created: 2015-10-01T05:40:04Z
http://www.live.bbc.co.uk/arabic redirects to http://www.live.bbc.com/arabic in the US (and probably other countries)
Is there a different URL you'd consider using so that config.yaml works out of the box?

Closing comment (2015-10-02T10:29:04Z): Thanks for reporting the issue. This is a duplicate of #283
Repository: bbc/wraith

Issue #507: [Feature request] Not include errors below threshold
Created: 2017-01-31T18:35:16Z
HI I guess this is more a feature request if possible? I have set threshold on runs for any pages with errors above 10% which works great - when it finishes its run it shows a report on screen of the pages that have errors above 10 but when it generates the gallery, it also includes the pages that errors below 10% in shots dir/gallery.html. Is there anyway to exclude those with less than 10% from being included? Thanks
Addition: Also not to include anything below threshold into the thumbnails gallery directory this just takes up space.

Duplicate issue #512: Gallery still shows diffs which are less then threshold set in "diff_only" mode
Created: 2017-03-09T11:25:35Z
Hi,
I have installed the latest version of Wraith via "gem install" on my Mac. It works as expected, however when setting the threshold to any value (e.g. 5%) and using "diff_only" mode, the gallery.html still shows all the diffs. I would expect the gallery to only display diffs above 5%.
Should the "diff_only" mode only show diffs or is it expected that it show all diffs?
Cheers,
Warren

Reporting a problem? Please describe the issue above, and complete the following checklist so that we can help you more quickly.
Issue checklist:


 I have validated my config file against YAML Validator to make sure it is valid YAML.


 I have run the wraith info command and pasted the output below:


paste results here


 I have run the command in verbose mode (by adding verbose: true to my config) and pasted the output below:

paste results here


 I have pasted the contents of my config file below:

paste config here

Closing comment (2017-03-09T11:29:16Z): Thanks for taking the time to raise an issue. This is a duplicate of #507.
Repository: bbc/wraith

Issue #318: Default screen height should be the documentHeight
Created: 2015-11-16T15:57:34Z
The default document height for screenshots is set to 1500px, this causes issues with some pages which are longer than this. Current workaround is to set something like:
screen_widths:

320x5000
600x5000
1024x5000

in order to get the full page in the screenshot. This obviously isn't ideal if we end up with a very long page.

Duplicate issue #535: Using phantomjs screenshot results don't show full page
Created: 2017-08-22T11:14:41Z
I tried to use phantomjs to grab some screenshots of our website before a design relaunch. Unfortunately, the screenshots are cropped as if the viewport isn't detected right. I have to use casperjs and the empty selector attribute to get it right. Now, it takes some time to set the spider file up, therefore I'd like to know if I missed out on something.
Issue checklist:
Output wraith info:
DEBUG: #################################################
DEBUG:   Command run:        info
DEBUG:   Wraith version:     4.0.1
DEBUG:   Ruby version:       ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
DEBUG:   ImageMagick:        Version: ImageMagick 7.0.6-4 Q16 x86_64 2017-07-29 http://www.imagemagick.org
DEBUG:   PhantomJS version:  2.1.1
DEBUG:   CasperJS version:   1.1.4
DEBUG: #################################################

Output in verbose mode:
Config validated. No serious issues found.
Creating Folders
SAVING IMAGES
DEBUG: phantomjs  '/Library/Ruby/Gems/2.0.0/gems/wraith-4.0.1/lib/wraith/javascript/phantom.js' 'https://www-de.scoyo.com//' '320,600x768,768,1024,1280' 'shots/home/MULTI_phantomjs_deutsch.png' 'body' '/Users/ijanson/Google Drive/scoyo/Qualitätsmanagement/Automated-Testing/wraith-2/javascript/wait--phantom.js' 'false'
Loading https://www-de.scoyo.com// at dimensions: 320x1500

Snapping https://www-de.scoyo.com// at: 320x1500

Resizing https://www-de.scoyo.com// to: 600x768

Snapping https://www-de.scoyo.com// at: 600x768

Resizing https://www-de.scoyo.com// to: 768x1500

Snapping https://www-de.scoyo.com// at: 768x1500

Resizing https://www-de.scoyo.com// to: 1024x1500

Snapping https://www-de.scoyo.com// at: 1024x1500

Resizing https://www-de.scoyo.com// to: 1280x1500

Snapping https://www-de.scoyo.com// at: 1280x1500

The contents of my config file:
---
imports: "spider_paths.yaml"

browser: "phantomjs"

domains:
  deutsch: "https://www-de.scoyo.com/"

before_capture: "javascript/wait--phantom.js"

screen_widths:
  - 320
  - 600x768
  - 768
  - 1024
  - 1280

resize_or_reload: "resize"

history_dir: "shots_base"

directory: "shots"

fuzz: "20%"

threshold: 5

gallery:
  template: "slideshow_template"
  thumb_width: 200
  thumb_height: 200

mode: diffs_first

verbose: true

highlight_color: red

phantomjs_options: ""

Closing comment (2018-09-07T20:01:17Z): This sounds like a dupe of #318
Repository: bcherny/json-schema-to-typescript

Issue #258: Feature request: dedupe emitted types referenced from multiple files
Created: 2019-09-17T21:32:54Z
Apologies if this has been asked before, I did a few searches but couldn't quite find this.
I have a directory of schemas. Each of those schemas sometimes share references to common definitions.
This tool automatically expands the references, and they all get in-lined (and thus duplicated).
It would be nice if references could be transformed to a typescript type, and referenced from a common file.
For example, 2 files might use:
{
  "myProp": { "$ref": "defs/my-prop.json" }
}
It would be really great if this were transformed to:
import { MyProp } from './defs/my-prop';

interface SomeObj {
  myProp: MyProp
}

Duplicate issue #579: Static imports for $refs
Created: 2024-02-07T16:08:52Z
Given structure like so:
schema/my-stuff.json :
{
   "id": "Stuff",
   "type": "object",
   "properties": {
      "someProp": {
         "$ref": "schema/enums/awesome-enum.json"
      }
  }
}

schema/enums/awesome.json :
{
  "id": "Awesome",
  "type": "string",
  "enum": [
    "FOO",
    "BAR"
  ],
  "tsEnumNames": [
    "FOO",
    "BAR"
  ]
}

When I run the following cli command:
npx json2ts --no-additionalProperties --no-enableConstEnums -i 'schema/**/*.json' -o packages/model/src/

I will get roughly this:
packages/model/src/awesome.ts :
export enum Awesome {
  FOO = "FOO",
  BAR = "BAR"
}

packages/model/src/my-stuff.ts :
export interface Stuff {
  someProp?: Awesome
}

export enum Awesome {
  FOO = "FOO",
  BAR = "BAR"
}

Awesome enum is now declared twice. And if I then reference this Awesome in any other schemas, it will be re-declared in every single file it is referenced.
Am I missing some way to import these instead? Or alternatively having everything in 1 file...

Closing comment (2024-06-25T12:39:42Z): Dup of #258
Repository: bcherny/json-schema-to-typescript

Issue #258: Feature request: dedupe emitted types referenced from multiple files
Created: 2019-09-17T21:32:54Z
Apologies if this has been asked before, I did a few searches but couldn't quite find this.
I have a directory of schemas. Each of those schemas sometimes share references to common definitions.
This tool automatically expands the references, and they all get in-lined (and thus duplicated).
It would be nice if references could be transformed to a typescript type, and referenced from a common file.
For example, 2 files might use:
{
  "myProp": { "$ref": "defs/my-prop.json" }
}
It would be really great if this were transformed to:
import { MyProp } from './defs/my-prop';

interface SomeObj {
  myProp: MyProp
}

Duplicate issue #276: Add option to "import" referenced schemas
Created: 2020-02-09T00:17:52Z
If I have the following schemas:
parent.json
{ 
    "title": "Parent",
    "properties": {
        "thing": {
            "$ref": "child.json"
        }
    } 
}

And child.json
{
    "title": "Child",
    "properties": {...}
}

It'd be really useful if the generated TypeScript file for "parent.d.ts" included an import for "child", based upon the reference path, e.g.:
import Child from './child'

export interface Parent {
    child?: Child;
}

This would greatly aid bulk compilation across a local schema ecosystem, without the code duplication of the TypeScript classes in all dependent files (I currently have a "Metadata" object exported by 14 different files in my codebase).

Closing comment (2020-05-17T19:28:53Z): This seems to be a duplicate of #258.
Repository: bcherny/json-schema-to-typescript

Issue #476: Generated types of referenced schemas are not imported
Created: 2022-07-30T16:51:53Z
Generated types of referenced schemas are not imported, instead they are output as:
{
  [k: string]: unknown;
}
maybe related #471

Duplicate issue #476: Generated types of referenced schemas are not imported
Created: 2022-07-30T16:51:53Z
Generated types of referenced schemas are not imported, instead they are output as:
{
  [k: string]: unknown;
}
maybe related #471

Closing comment (2022-07-30T17:01:21Z): I fixed the { [k: string]: unknown; } with oneOf.
Though the types are still not imported, but instead included and duplicated in each file.
Sp probably related to #476
Repository: bcherny/json-schema-to-typescript

Issue #337: Support propertyNames with enum
Created: 2020-09-08T18:10:23Z
propertyNames is included in the "not expressible in TS" list, but at least for the case with enum instead of pattern, this is not true. Consider the following example:
{
  "type": "object",
  "title": "workingHours",
  "definitions": {
    "weekdays": {"type": "string", "enum": ["monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday"]}
  },
  "additionalProperties": {"type": "number"},
  "propertyNames": {"$ref": "#/definitions/weekdays"}
}

could well be expressed in TS as
enum weekdays {
  monday = "monday",
  tuesday = "tuesday",
  wednesday = "wednesday",
  thursday = "thursday",
  friday = "friday",
  saturday = "saturday",
  sunday = "sunday"
}
type workingHours = {[k in weekdays]: number};

The example also shows what would be the purpose of this instead of specifying the properties literally: weekdays does not have to be repeated all the time when there are more types making use of its keys.

Duplicate issue #354: Export enum name to allow for casting
Created: 2020-12-15T21:16:56Z
The following JSON schema
"fruit": {
      "description": "type of fruit",
      "type": "string",
      "enum": [
        "BANANA",
        "KIWI",
        "CHERRY
      ]
    }

is converted to
fruit: "BANANA" | "KIWI" | "CHERRY"

in the generated interface.
That looks good, but this means you can't assign a string (even when the string is "BANANA", "KIWI" or "CHERRY") to an object that adheres to the interface, unless you cast it. However, without the d.ts file exporting the enum type there's no way you can actually cast the string to the enum.
The problem can be solved when json-schema-to-typescript would export the enum as follows
export enum fruit {
  BANANA = "BANANA",
 KIWI = "KIWI",
 CHERRY = "CHERRY"
}

because that would allow consumers of the interface to cast a string to the enum as follows
...
fruitPropertyOfObjectThatShouldAdhereToInterface: <fruit> fruitString,
...

Am I missing something or would this be a much needed improvement?

Closing comment (2020-12-30T09:35:41Z): I think it's a really important principle not to have to rely on custom properties in your input JSON schema to end up with an exported named enum in TypeScript that you can use for casting your strings when coding.
As mentioned before this is similar to #337 and actually exactly the same as #200 with 6 upvotes and a pull request that was never merged (#262)
Repository: bcherny/json-schema-to-typescript

Issue #335: Feature request: Configuration option to disable generation of `[k: string]: unknown`
Created: 2020-08-31T07:33:27Z
Hi,
Would you consider adding a config option to disable generation of [k: string]: unknown; if additionalProperties is not explicitly set to false?
I understand that technically the current behavior is correct as it follows the spec but [k: string]: unknown; allows referencing any arbitrary properties and makes it difficult to catch errors at compile time.

Duplicate issue #346: Add global `additionalProperties` config
Created: 2020-10-31T17:53:37Z
How to remove all [k: string]: unknown;
export interface MySchema {
  code: number;
  msg: string;
  data: {
    demo: string;
    field_1: string[];
    field_2: number[];
    field_3: {
      field_4: number;
      [k: string]: unknown;
    }[];
    [k: string]: unknown;
  };
  [k: string]: unknown;
}

Closing comment (2020-11-29T23:37:25Z): Dup of #335
Repository: bcherny/json-schema-to-typescript

Issue #258: Feature request: dedupe emitted types referenced from multiple files
Created: 2019-09-17T21:32:54Z
Apologies if this has been asked before, I did a few searches but couldn't quite find this.
I have a directory of schemas. Each of those schemas sometimes share references to common definitions.
This tool automatically expands the references, and they all get in-lined (and thus duplicated).
It would be nice if references could be transformed to a typescript type, and referenced from a common file.
For example, 2 files might use:
{
  "myProp": { "$ref": "defs/my-prop.json" }
}
It would be really great if this were transformed to:
import { MyProp } from './defs/my-prop';

interface SomeObj {
  myProp: MyProp
}

Duplicate issue #553: Create `index.ts` when generating files from a directory
Created: 2023-09-26T12:42:05Z
I'm using the CLI as follows:

json2ts -i './*.json' --output -o ../contracts

Where in my current directory there are multiple JSON Schema files. In the contracts directory I'm getting multiple d.ts files. I'd like to be able to reference them together, and to autogenerate an index.ts file while will re-export everything inside the directory.
If there's an easier way to achieve that I would be happy to hear about it.
Thank you

Closing comment (2024-01-14T03:01:35Z): Dup of #258
Repository: bcherny/json-schema-to-typescript

Issue #124: Inspect Pattern Properties just for recursive definitions.
Created: 2017-10-23T05:32:30Z
I just want to make it initially clear: I'm not looking for you to generate code for patternProperties.
However, pattern properties do reference definitions that would be good to generate samples for. For example, in swagger we have the following definition:
  "paths": {
    "type": "object",
    "description": "Relative paths to the individual endpoints. They must be relative to the 'basePath'.",
    "patternProperties": {
      "^x-": {
        "$ref": "#/definitions/vendorExtension"
      },
      "^/": {
        "$ref": "#/definitions/pathItem"
      }
    },

Since this definition relies exclusively on patternProperties the generated object looks like this:
/**
 * Relative paths to the individual endpoints. They must be relative to the 'basePath'.
 */
export interface Paths {

}

I think that we can all agree that this is not very useful. Frankly, a more useful implementation would be:
/**
 * Relative paths to the individual endpoints. They must be relative to the 'basePath'.
 */
export interface Paths {
    [name: string]: VendorExtension | PathItem;    
}

But, like I said, I don't really want to solve that problem here. The real problem is that VendorExtension and PathItem are never generated at all.
This means that I can't even do some minor edits, after the fact, to the generated code, to make it behave as I expect. It would be really could if you could scan the patternProperties just to continue the code generation so the resultant file was easier to modify to be correct.
Would that be an acceptable compromise? That way, you don't need to solve the patternProperties problem but users of your excellent tool could get 95% of the way to fully generated code instead of 60% of the way there in examples that make heavier use of patternProperties.

Duplicate issue #129: Generating patternProperties Objects
Created: 2017-11-11T14:02:22Z
Is this schema:
{
  "id": "Parent",
  "type": "object",
  "patternProperties": {
    "^[a-zA-Z]+": {
      "id": "Child",
      "type": "object",
      "properties": {
        "aProperty": { "type":"string" }
      }
    }
  }
}

not supposed to generate a Child interface? I tested it out on https://bcherny.github.io/json-schema-to-typescript-browser/ and it only returned a Parent interface, i.e.
export interface Parent {
  [k: string]: any;
}

If not, is there any way to force json-schema-to-typescript to generate an interface for ALL objects, regardless of whether or not a specific portion of the JSON Schema specification can be supported in Typescript?

Closing comment (2017-11-11T20:12:00Z): I see. I believe this is a duplicate of #124. Feel free to reopen if you feel otherwise.
Repository: bcherny/json-schema-to-typescript

Issue #258: Feature request: dedupe emitted types referenced from multiple files
Created: 2019-09-17T21:32:54Z
Apologies if this has been asked before, I did a few searches but couldn't quite find this.
I have a directory of schemas. Each of those schemas sometimes share references to common definitions.
This tool automatically expands the references, and they all get in-lined (and thus duplicated).
It would be nice if references could be transformed to a typescript type, and referenced from a common file.
For example, 2 files might use:
{
  "myProp": { "$ref": "defs/my-prop.json" }
}
It would be really great if this were transformed to:
import { MyProp } from './defs/my-prop';

interface SomeObj {
  myProp: MyProp
}

Duplicate issue #629: Allow for deduplication
Created: 2024-09-03T03:27:43Z
I have a bunch of schemas for different responses from a API: https://github.com/Bluscream/grayjay-source-pietsmietde/tree/master/schemas/pietsmiet.de
And i would like to be able to convert them to .d.ts files, but the problem is that some of them include duplicates (a type being used by multiple responses and therefor in multiple

Closing comment (2024-09-03T03:30:08Z): Dup of #258
Repository: bcherny/json-schema-to-typescript

Issue #299: additionalProperties can create invalid typings
Created: 2020-05-08T00:35:03Z
The following schema:
{
  "properties": {
    "s": { "type": "string"}
  },
  "additionalProperties": {
    "properties": {
      "foo": {"type" : "string"}
    }
}
produces this typing:
/* tslint:disable */
/**
 * This file was automatically generated by json-schema-to-typescript.
 * DO NOT MODIFY IT BY HAND. Instead, modify the source JSONSchema file,
 * and run json-schema-to-typescript to regenerate this file.
 */

export interface FooSchema {
  s?: string;
  [k: string]: {
    foo?: string;
    [k: string]: unknown;
  };
}
Which produces this tsc error:
foo.d.ts:9:3 - error TS2411: Property 's' of type 'string' is not assignable to string index type '{ [k: string]: unknown; foo?: string; }'.

Duplicate issue #477: strictIndexSignatures appears to be broken since at least v11.0.0
Created: 2022-08-01T08:15:45Z
Per the title, it seems the strictIndexSignatures option has no effect since v11.0.0.
The below script fetches the latest JSONSchema for NPM's package.json file and attempts to generate types for it. In spite of the strictIndexSignatures: true at line 20, I still get errors like the following:
lib/types.ts:15788:3 - error TS2411: Property 'require' of type 'PackageExportsEntry | PackageExportsFallback | undefined' is not assignable to 'string' index type 'PackageExportsEntry | PackageExportsFallback'.

15788   require?: PackageExportsEntry | PackageExportsFallback;

The script in question (depends on got to fetch the schema) is here:
import { resolve as pathResolve, join as pathJoin } from "path";
import { writeFileSync } from "fs";

import got from "got";
import { compile } from "json-schema-to-typescript";
import type { JSONSchema4 } from "json-schema";

const url =
  "https://raw.githubusercontent.com/SchemaStore/schemastore/master/src/schemas/json/package.json";
const outputPath = pathJoin(pathResolve(__dirname, "..", "lib"), "package-json-types.ts");

(async function () {
  try {
    console.log(`Fetching updated JSONSchema for package.json from ${url}`);
    const schema = (await got(url).json()) as JSONSchema4;

    console.log("Converting JSONSchema to TypeScript interfaces");
    const result = await compile(schema, "PackageJson", {
      unreachableDefinitions: true,
      strictIndexSignatures: true,
    });

    console.log(`Writing interfaces to ${outputPath}`);
    writeFileSync(outputPath, result, { encoding: "utf8" });
  } catch (err) {
    console.error(err);
    process.exit(1);
  }
})();

Closing comment (2022-08-06T08:51:06Z): This is a dup of #299. Suggestions welcome!
Repository: bcit-ci/CodeIgniter

Issue #218: Reverse routing
Created: 2011-08-20T20:38:41Z
There's is an existing pull request that supports reverse routing and matches parenthesis.

Duplicate issue #1293: feature request for reverse routing 
Created: 2012-04-26T03:45:26Z
New to php and CI... I would hate to hard-code url in my template. a way to reverse mapping the routes from config/routs.php would be really nice.
Looks like there isn't such feature in CI and I found one here http://codefury.net/2010/09/easy-reverse-routing-with-codeigniter/   it is "an extension for the CodeIgniter Router class that I wrote that gives you a nice way to write routes that are reversible and also have the ability to take parameters."
What do you think?

Closing comment (2014-10-28T20:13:09Z): Closing this as duplicate of #218.
Repository: bcit-ci/CodeIgniter

Issue #186: DBUtil->backup, not escaped table name in _backup MySQL driver
Created: 2011-08-19T14:49:53Z
Within the MySQL utility driver method '_backup' several SQL queries do not escape the $table name, SQL statements on lines 99, 112, 132 & 199. This is done throughout so much of the Database class I was surprised by this ommission.
Adding ` around each $table resolved the potential error of Reserve word table name clashes. Granted, not an excellent database schema practice but an error waiting to happen all the same.
I have also found this applies to both version 2.0.2 & 1.7.2.

Duplicate issue #1984: Database _backup function is missing escape character when getting table data
Created: 2012-11-07T17:29:59Z
File Location: system/database/drivers/mysql/mysql_utility.php
line 132 needs escape ` around $table
Currently look like this
$query = $this->db->query("SELECT * FROM $table");
Should look like this
$query = $this->db->query("SELECT * FROM $table");

Closing comment (2012-11-07T18:57:57Z): Duplicate of #186, #1879. Already fixed in develop.
Repository: bcit-ci/CodeIgniter

Issue #4210: $this->form_validation->run() with no rules fails, used to pass
Created: 2015-11-04T01:31:21Z
I have a form with 3 arrays of checkboxes. It is acceptable for none of the checkboxes to be checked, some of them to be checked, or all of them to be checked.
The rules array looks like this:
$config['THE_FORM_VALIDATION_RULES'] = array(

   array('field' => 'allowed[]', 
         'label' => 'Allowed', 
         'rules' => ''), 

   array('field' => 'chosen[]', 
         'label' => 'Chosen', 
         'rules' => ''), 

   array('field' => 'default_checked[]', 
         'label' => 'Default Checked', 
         'rules' => ''), 

   );

There are no rules for any of the 3, because, again, it is allowable for none of the checkboxes to be checked. However, each entry has to be there so that the form data can be repopulated on error (without them, form repopulation does not work);
In the CI 2.x branch, a call to $this->form_validation->run() with these rules would pass. In the 3.x branch, it fails.
I have tracked the failure back to a chunk of code in Form_validation set_rules:
        // No fields or no rules? Nothing to do...
        if ( ! is_string($field) OR $field === '' OR empty($rules))
        {
            return $this;
        }
        elseif ( ! is_array($rules))
        {
            // BC: Convert pipe-separated rules string to an array
            if ( ! is_string($rules))
            {
                return $this;
            }

            $rules = preg_split('/\|(?![^\[]*\])/', $rules);
        }

CI 2.x simply did this:
        // No fields? Nothing to do...
        if ( ! is_string($field) OR  ! is_string($rules) OR $field == '')
        {
            return $this;
        }

For the moment, I can get away with making 'allowed[]' be required, but it would be more correct for it to work with no rules for any of the 3 entries.
Perhaps there is some other rule I am missing that could describe an array of numeric values?

Duplicate issue #4619: Validation error message for 'matches' rule uses field name instead of 'human' name
Created: 2016-05-06T14:52:24Z
I have two fields for changing a password, with the following rules in my controller:
$this->form_validation->set_rules('new_password', 'New Password', '');
$this->form_validation->set_rules('confirm_new_password', 'Confirm New Password', 'matches[new_password]');

If there is a mismatch, the validation error message is:

The Confirm New Password field does not match the new_password field.

I'm sure it never used to be like this?
I'm using CI 3 (can't seem to find a specific version number in the code anywhere)

Closing comment (2016-05-11T20:45:21Z): Duplicate of #4210.
Repository: bcit-ci/CodeIgniter

Issue #4209: system/core/Config.php 3.0 There is an error in line 89
Created: 2015-11-03T03:35:41Z
// Set the base_url automatically if none was provided
if ($this->config['base_url'] == '')
{
if (isset($_SERVER['HTTP_HOST']))
{
$base_url = isset($_SERVER['HTTPS']) && strtolower($_SERVER['HTTPS']) !== 'off' ? 'https' : 'http';
$base_url .= '://'. $_SERVER['HTTP_HOST'];
$base_url .= str_replace(basename($_SERVER['SCRIPT_NAME']), '', $_SERVER['SCRIPT_NAME']);
}
        else
        {
            $base_url = 'http://localhost/';
        }

        $this->set_item('base_url', $base_url);
    }

Duplicate issue #4361: If base_url is empty,When using VHOST, there will be some inconvenience. for 3.03
Created: 2016-01-06T05:02:15Z
If base_url is empty, Config will automatically generate this value, using SERVER_ADDR to replace the HTTP_HOST, resulting in the system link and access to the domain name of the link is not consistent. When using VHOST, there will be some inconvenience.
For example:
access to http://localhost/,
base_url=http://127.0.0.1/ in the system

Closing comment (2016-01-06T11:19:49Z): Duplicate of #4209, #4226, #4231.
Won't be changed even if a thousand more people complain about it - security has higher priority.
Repository: bcit-ci/CodeIgniter

Issue #949: Checkbox setting ignored if Form validation in use and checkbox not being validated.
Created: 2012-01-22T06:28:28Z
I have a registration form with multiple fields on it including two checkboxes. Most of the fields are validated (they're required) but I have a ONE checkbox that is optional and doesn't need to be validated so no rules are set for it.
When there's an error on the form I redisplay it and every field is redisplayed with the value set by the user EXCEPT the checkbox that wasn't validated.
Investigation in the library code suggests that the problem is due to the fact that there are two set_checkbox functions: one in  form_helper.php which is globally available and one as a method in form_validation.php. The global set_checkbox function checks to see if the form_validator object is available and if so just hands  control to it even if the field in question is NOT being validated. And since the form_validation object only contains POST information about fields that are being validated, the original value of any field (such as my checkbox) that has no validation rule is lost.
I've fixed the problem by altering the library code for the form validator and it's attached to this message. However it's pretty quick and dirty and someone who is more familiar with the form validation code might find a better solution.
I got around the problem by simply dumping the logic from the global set_checkbox function (which reads the $_POST array directly) into the section of the set_checkbox method that deals with the field not being found in the _field_data array.

Duplicate issue #1961: Form Validation with Form Helper
Created: 2012-11-02T17:31:47Z
In the Form Helper, when you use the functions of set_value, set_select, set_checkbox, it checks if the Form Validation object has been called. It if has been called, it pulls values from the Form Validation object.
The problem comes, when one has called the form validation object, and the form helper. But in the form validation object, a certain person may not setup the rules for all input elements of the form. This can create quite a headache for a person who didn't know that if you use the form validation library, you need to set rules for all of them or else you cannot repopulate the whole form.
Now for certain elements, no rule is required, simply because they are optional.
Perhaps, the form library and form helper functions needs to be separated, or at least in the User Guide, there needs to be a clear notice saying that one needs to set all the rules for all the inputs when using form validation while repopulating the form.
One more note, set_radio and set_checkbox will echo out "checked" =  "checked". This defeats the purpose of using form_checkbox or form_radio. Since you now need to use the normal html to have those activated. On the other hand, set_value just gives the value, it does not echo out "value = XXXX". This is inconsistent, if we want to make the form_helper useful, all three should either only give out a value only like set_value, or echo out a string like the other sets.

Closing comment (2012-11-02T18:44:49Z): Duplicate of #949.
Repository: bcit-ci/CodeIgniter

Issue #5462: Query Builder LIKE BEFORE doesnt work CI 3.1.8
Created: 2018-04-02T14:17:23Z
There is an issue with LIKE method of query builder class when 'BEFORE' parameter is passed.
This code generates database error :
$this->db->select('*')->like('id', 'zefzefezf', 'BEFORE')->get('email_v2');
Result :
SELECT * FROM email_v2 WHERE id LIKE %'zefzefezf' ESCAPE '!'
The 'BOTH' and 'AFTER' parameter are working properly.

Duplicate issue #5469: [ bug]ci v3.1.8 like use before
Created: 2018-04-11T12:26:00Z
system\database\DB_query_builder.php
find
protected function _like(
case 'before':
$v = "%'{$v}'";
change
case 'before':
$v = "'%{$v}'";

Closing comment (2018-04-13T10:52:01Z): Duplicate of #5462.
Please search for existing issues before posting.
Repository: bcit-ci/CodeIgniter

Issue #193: Array Validation with Callback-function. Form Validation Class
Created: 2011-08-19T14:50:50Z
It might be useful to somehow extend usual array validation (in Form Validation Class) using callback-function.
Handling <input type="checkbox" name="field[]" value="val" /> with this code:
$this->form_validation->set_rules('field[]', 'field_name', 'callback_check_field');
passes to the callback function every element of "field" individually, and the quantity of function calls equals to the quantity of elements in array.
Validation of the same html input with this code:
$this->form_validation->set_rules('field', 'field_name', 'callback_check_field');

passes to the callback function the whole array "field", and the quantity of function calls still equals to the quantity of elements in array.
It's not good when, for example, in callback function there is a db request $this->db->where_in($field)->... or something.
It would be great to have possibility to validate the whole array at once, with only one callback-function call.

Duplicate issue #2235: Call callback function to html array inputs only once and pass the value as array
Created: 2013-02-10T16:36:01Z
If a create a custom callback function for html array input forms, for the form validation library the callback function is called separately for each input. I guess it would be more convenient in many cases if the callback is called only once and the value to check against is passed as an array.
In my case I have a form which has three inputs for phone number and only one of them (no matter which) is mandatory. If I set a rule like this:
$this->form_validation->set_rules('phone', 'Phone Number', 'required');
the validation always fails if there is at least one field empty. This also can't be achieved using the custom callback function, because I never know the previous or next value from the input array. If I had an array $phones that includes all the values of inputs with a name phone[] I could easily validate only the non empty fields.

Closing comment (2013-02-10T18:32:47Z): Duplicate of #193.
Repository: bcit-ci/CodeIgniter

Issue #3487: Bug in Upload library
Created: 2015-01-20T15:28:51Z
Bug in Upload library
Upload library throw:
Severity: Notice --> Undefined property: Upload::$upload
Even after being included.

Duplicate issue #3489: Bug in Upload library
Created: 2015-01-20T16:46:02Z
Sorry for insisting
I tried with CodeIgniter-develop 3.0 and fail, it throws the message: Undefined property: Upload::$upload.
This works in the previous versions (CodeIgniter 2.x)

Upload library throw:
Severity: Notice --> Undefined property: Upload::$upload
Even after being included.

Closing comment (2015-01-20T16:49:32Z): Do not open another issue, please. This is a duplicate of #3487.
Repository: bcit-ci/CodeIgniter

Issue #5350: session 文件unlink错误
Created: 2017-12-06T06:24:51Z
当程序执行session的gc函数的时候，出现warning unlink(/var/lib/php/session/ci_session398713f044003b888df479c96bd27010820f1053): No such file or directory。检查确实session文件不存在，但是程序里面已经判断了，为什么还是会出现这样的错误？？

Duplicate issue #5351: There is a warning when unlink session files "No such file or directory"
Created: 2017-12-06T08:56:22Z
Hi,
I found there is a warning message "unlink(/var/lib/php/session/ci_session398713f044003b888df479c96bd27010820f1053): No such file or directory" in logs. But I check that if there is a session file before executing unlink session files.

Best,
Tyler Teng

Closing comment (2017-12-06T11:27:52Z): No such code exists in CodeIgniter.
Note that this is a bug tracker; we don't provide help for code that you write here. Please post your questions on our forums instead.
Also, post actual code instead of screenshots.
(duplicate of #5350)
Repository: bcit-ci/CodeIgniter

Issue #4995: Ajax login issue
Created: 2017-01-25T15:26:59Z
Hi! I am trying to make a login using ajax, but when i want to save the session data, it shows me that everything is set, but when i refresh the page everything is lost and my session data it is empty. Do you have any idea to help me in this problem? I am using C.I 3

Duplicate issue #4996: Setting session using ajax not working
Created: 2017-01-25T19:25:22Z
Hi! I just try to set some session variable using ajax code, but from what ive discovered the data i set are not keept on the next screen refresh. Do you have any idea how to solve this. Im pretty sure it is a codeigniter session management bug.

Closing comment (2017-01-25T19:29:45Z): Duplicate of #4995.
Please stick to my advice about posting on the forums instead. Just saying the word "bug" doesn't change a thing.
Repository: beakerbrowser/beaker

Issue #11: Restore scroll-position on back/forward
Created: 2016-06-26T22:13:01Z
Clicking back/forward should scroll you to your last position.

Duplicate issue #514: Restore previous scroll position on back/forward
Created: 2017-06-07T19:02:04Z
Pretty obvious feature: when you navigate through history, it's helpful if the scroll position is restored to its previous point that the user had before they navigated away.

Closing comment (2017-11-09T23:38:49Z): This is a duplicate of #11
Repository: beakerbrowser/beaker

Issue #1005: Feature Request: Forking Non-DAT Archive Websites
Created: 2018-05-26T04:12:26Z
I'd like to be able to access an HTTP website in the same way as I would a DAT archive. Namely, I'd like to have a local copy of the site that I can access even when I don't have a reliable or fast internet connection. A naive approach would be to use a tool like HTTrack (GPL) to clone a website and then convert that into a DAT archive. I think if this is integrated into the UX of beaker in a similar way to the forking of dat sites, this can be a functional solution that takes advantage of the existing DAT archive features.

Duplicate issue #1187: Feature: Add "Make editable copy" to legacy https / http pages as well.
Created: 2018-10-03T20:44:43Z
On multiple occasions I found myself using "Save Page As..." feature (in Firefox, one in beaker doesn't seems to work) and then adding saved page (dir containing all the assets) to beaker library.
It is was useful in one instance as it allowed me to share meetup schedule where internet connectivity was spotty. On other instances I just wanted to pin down the page for later consumption.
I think beaker has opportunity to allow capturing arbitrary pages into library if it were to combine contents.savePage Electron API with starting a new archive feature.
Would be even more cool to expand support for this to DatArchive.fork to let apps do more interesting things with it.
This has come up in dat://fritter.hashbase.io/thread/dat://453c8faa21215ad8da5970ecce16474515d298963953e733b4520c25992ee906/posts/0jmthmg6m.json

Closing comment (2018-11-19T17:11:07Z): Maybe duplicate of: #1005
Repository: beakerbrowser/beaker

Issue #1600: Watch folder support
Created: 2020-05-16T12:56:54Z
Is your feature request related to a problem? Please describe.
In previous releases of Beaker browser, it was possible to create a site from a local folder on my computer and for the browser to watch the folder for changes. It would be really nice if this feature was reintroduced so that when I build and export my local site (I am using Next.js) that the site updates automatically.
Describe the solution you'd like
Reintroduction of the watch folder for changes functionality.
Describe alternatives you've considered
I've considered recreating the site each time but that seems like a lot of manual effort and will cause the URL to change.
Additional context
Perhaps I am misunderstanding how the protocol is supposed to function and I should instead rely on a new Beaker API.

Duplicate issue #1641: Shared drive does not update with new additions
Created: 2020-05-20T21:29:58Z
Maybe I am confused as to how the new Beaker works but from my previous use I would share a folder and then Beaker will keep an eye on that folder and whatever I would add there, Beaker will index. It was a dynamic folder sharing. Now it does not update/index the folders that I share via New Hyperdrive or New Drive From Folder. I also checked the structure of the folder and the merge/dif section and is nothing there. I can add stuff to this folder but Beaker does not index it.
Is Beaker working differently now?

Closing comment (2020-05-21T23:40:55Z): Yeah this is actually a dup of #1600. Going to close this issue to keep the number of open issues down.
You're right, we did lose a good feature on this one. The reason is a long story but that doesn't matter: point is that we do want to get this feature back and we're just working on the right way to do it. Sorry for the temporary loss!
Repository: beakerbrowser/beaker

Issue #1035: Dark mode UI
Created: 2018-06-07T15:25:17Z
Operating system: Windows 10 Pro x64 | Fedora 31 Workstation
This is: a GUI feedback.
Would be niceful a "dark" theme or mode (like Monokai theme or DuckDuckGo dark theme). BTW, Interface is very clean and simple, I love it. Good job.

Duplicate issue #1471: dark mode
Created: 2019-10-18T23:23:54Z
Operating system: manjaro linux
This is:

 a bug
[ x] general feedback
i have low vision

i would love to see a dark theme option inside beaker. i currently use firefox and have it tweaked so its respecting my dark theme and together with a darkreader plugin this works 99% of the time.
beaker is electron app and defaults to a standard GTK or QT white theming?. because its sandboxed frm the os ?
would be nice to see a GTK/QT theme chooser.

Closing comment (2019-11-12T21:23:05Z): Duplicate of #1035