primordic/IssueDupesLite huggingface dataset:
Repository: userfrosting/UserFrosting

Issue #921: Update vulnerable handlebars@^3.0.3 to ^4.0.12
Created: 2019-01-11T11:02:22Z
Handlebars ^3.0.3 is affected by https://nodesecurity.io/advisories/61 (cross-site scripting)
We should update to ^4.0.12 if possible.

Duplicate issue #949: Upgrade Handlebar to version >=4.0.0
Created: 2019-03-16T20:46:37Z
UF currently uses Handlebar 3.x, which contains a security vulnerability. We should see to upgrade ASAP to 4.1.x

The handlebars package before 4.0.0 for Node.js allows remote attackers to conduct cross-site scripting (XSS) attacks by leveraging a template with an attribute that is not quoted.

https://nvd.nist.gov/vuln/detail/CVE-2015-8861
https://github.com/wycats/handlebars.js/blob/master/release-notes.md

Closing comment (2019-03-26T07:51:10Z): Duplicate of #921
This won't be deliverable in a 4.2.x milestone either, because its a breaking change.
Repository: userfrosting/UserFrosting

Issue #439: Point System
Created: 2015-10-28T09:55:54Z

Duplicate issue #458: Found a points / levels / badges system perfect for UF
Created: 2015-11-08T09:52:24Z
https://github.com/Editandrew/PHPGamification

Closing comment (2016-01-06T19:46:28Z): Closed as duplicate of #439
Repository: userfrosting/UserFrosting

Issue #961: NPM Error with Homestead installation
Created: 2019-04-08T22:40:17Z
Another user mentioned they had a NPM error when trying to install a fresh copy following the instructions here.
I was able to reproduce this error myself on Windows 10 machine and am adding the error messages in the attached file.
UserFrostingHomesteadError.txt

Duplicate issue #1049: NPM dependency installation error
Created: 2019-11-05T15:11:58Z
Hi, first time installing UserFrosting on Windows via Bash. I followed instructions in Installation thread on the official web site. I use Vagrant/Homestead. After running vagrant up, i got an error on new created site which looks like this:

Then i followed vagrant ssh command, then php bakery bake. This error showed up.

As i read forums and stacks, i discovered it is Windows problem with symbolic links. I tried to install acorn with --no-bin-links, and installation was successfull. Although i run the php bakery bake command again and the error still showed up. Do you have any suggestions what could be the solution to this type of error? All help is welcomed. Thank you!

Closing comment (2019-11-05T15:22:09Z): Possible duplicate of #961 also
Repository: userfrosting/UserFrosting

Issue #665: Disabling CSRF guard for specific routes
Created: 2017-03-14T21:12:24Z
Sometimes, you need to exclude certain routes from CSRF checks.  For example, routes that are meant to be consumed by another application instead of a browser (see #385, #521, #558, #568).  It's also useful for things like raw asset loading, where you want to avoid initializing the CSRF middleware altogether, because it has a dependency on session - which in turn can cause too many read/write attempts in succession, as we saw with #633.
One option is to disable global CSRF middleware, and instead require that each route explicitly declare the CSRF check as route middleware ("whitelist" approach).  I'm not sure if this would still end up initializing the middleware on routes that don't actually use it.
Or, we can leave global CSRF middleware enabled, and then provide a means for routes to declare themselves exempt from CSRF checks ("blacklist" approach).  Again, we'd want to check the blacklist before the middleware is even instantiated in the first place.
You can see how we're implementing blacklisting for asset routes right now:
// Middleware
// Hacky fix to prevent sessions from being hit too much: ignore CSRF middleware for requests for raw assets ;-)
// See https://github.com/laravel/framework/issues/8172#issuecomment-99112012 for more information on why it's bad to hit Laravel sessions multiple times in rapid succession.
$request = $container->request;
$path = $request->getUri()->getPath();
$csrfBlacklist = [
    $container->config['assets.raw.path']
];
if (!$path || !starts_with($path, $csrfBlacklist)) {
    $app->add($container->csrf);
}

So, maybe we could just go with a blacklist, and build a wrapper around it so that it doesn't have to do this in index.php?
This is also related to #617.

Duplicate issue #706: Support non-standard CSRF sources
Created: 2017-05-14T11:18:23Z
Standards such as OAuth provide a means to implement CSRF protection, but currently UserFrosting can't be easily adapted (and by easily, I mean via Sprinkles) to provide protection in these scenarios.
My idea for this, is a series of callbacks that are executed before the Slim CSRF middleware kicks in, which inspect the request for CSRF protection values wherever they may be stored, returning true if the CSRF is found. If true is returned, some code would inject the CSRF values, ready for Slim CSRF to take over.

Closing comment (2017-05-14T15:43:36Z): Possibly related to #665.
Repository: userfrosting/UserFrosting

Issue #680: Hardcoded redirect to `dashboard`
Created: 2017-04-02T17:30:18Z
See #677.
By default, every role has some sort of access to the dashboard page, but the problems is a user might not have access to the dashboard if the dev change that behavior.
The redirect link should be defined in a RedirectHandler class or something like that which people can override as needed, similar to the redirect after login.

Duplicate issue #707: Landing page hard-coded
Created: 2017-05-15T13:53:33Z
Creating new user sends an email to the new user. After setting new password, they are being brought to dashboard. If default users' permission to dashboard is being removed, error would occur.
the redirect should use $this->ci->determineRedirectOnLogin service instead of hard-coded redirect so that it's easier to overwrite. The best would be loading "default landing location" from config file instead.

Closing comment (2017-05-15T14:07:13Z): Duplicate #680
Repository: userfrosting/UserFrosting

Issue #763: Creating new User requires Email support
Created: 2017-07-09T18:11:21Z
When creating a user in the admin dashboard UF currently enforces the use of email. If your config is missing or incorrect the creation of the user fails. This can be an issue for development as the developer may have chosen to not setup email support. I do this frequently for a few reasons.
Solution
Allow the user to be created with an option to not send an email. In which case a random password would be generated. A second possible solution, if email was opted out, create the user and leave the password blank. The user would remain inactive and the admin would have to manually (re)set the password and then enable the user.
This would of course leave 'flag_verified' as negative and flag_enabled as negative to start. However, if email was opted out, simply mark 'flag_verified' as 1 for true. Manually enabling the account would set the 'flag_disabled' to 1.
This would allow for for expansion into a 'customer' type model or simply easier on the developer lol.

Duplicate issue #552: Handling SMTP errors on user creation
Created: 2016-06-05T01:40:30Z
I tried to create a new user from the admin panel on a fresh install with incorrect SMTP credentials, and the site just hung.  I think for whatever reason, that error wasn't being caught and dealt with appropriately.

Closing comment (2018-10-28T20:48:06Z): Duplicate of #763.
Repository: usual2970/certimate

Issue #22: 希望可以支持自定义证书厂商
Created: 2024-09-12T07:46:23Z
比如说腾讯云就有api可以获取ssl证书

Duplicate issue #557: 增加证书申请渠道
Created: 2025-03-25T06:12:46Z
功能描述 / Description
能否支持阿里云华为云等云服务商申请证书
请求动机 / Motivation
可以直接管理多云服务商的证书无需登录一 一查看
其他 / Miscellaneous
No response
贡献 / Contribution

 我乐意为此贡献代码！ / I am interested in contributing to this feature!

Closing comment (2025-03-25T08:20:51Z): duplicate #22
Repository: usual2970/certimate

Issue #404: [Feature] 部署怎么对外访问 现在只能本地访问 127.0.0.1
Created: 2025-01-07T03:41:29Z
版本 certimate_0.2.21_linux_amd64
linux部署怎么对外访问 现在只能本地访问 127.0.0.1 启动要加什么配置么

Duplicate issue #417: [Feature] 只能通过本机访问吗
Created: 2025-01-15T00:53:03Z
只能通过本机访问，不能通过其他的机器访问吗

Closing comment (2025-01-15T01:13:15Z): duplicate #404
Repository: usual2970/certimate

Issue #519: [Feature] 工作流通知模块增加默认通知模板和预设变量
Created: 2025-03-14T04:02:24Z
功能描述
目前工作流的通知模板中，没有预设的通知模板，每一个工作量都需要根据内容自定义。希望能实现如下功能：
1.新增一个默认的通知模板，同时预设变量如：域名、证书申请情况、证书部署情况等变量,如：
通知主题：${workloadExecutionStatus}（X工作流执行成功；X工作流执行失败；）
通知内容：
${DOMAINS}域名证书申请和部署情况如下：
证书申请结果：${certificateApplicationStatus} 【申请成功；申请失败，失败原因${applicationFailure}】
证书部署结果：${certificateDeploymentStatus} 【部署成功，已经部署至于${deploymentTarget}；部署失败，失败原因${deploymentFailure}】
工作流执行时间：${time}
动机
增加通知可读性，了解具体工作量情况。
替代方案
通过执行结果分支实现一定需求的执行情况通知（只能固定字段）。
其他信息
暂无

Duplicate issue #528: [Feature] 工作流的通知模板能否引入变量
Created: 2025-03-17T06:27:29Z
功能描述
当证书到期并成功部署时发送通知：域名 ${DOMAINS}已成功更新证书。
动机
个人感觉当前的工作流的通知部分只有纯文本比较单一。

Closing comment (2025-03-17T06:50:30Z): duplicate #519
Repository: usual2970/certimate

Issue #92: [Feature] 建议减少api接口中返回数据
Created: 2024-09-24T09:27:30Z
功能描述
建议减少api接口中返回的数据，尤其是相对敏感的数据。
动机
主要是为了数据安全。
替代方案
比较重要的是：record接口中返回apikey和apisecret，还有域名列表中ssl证书的公钥、私钥和证书地址。界面上没有展示相关的信息，也没有展示的必要，建议削减。尤其是apikey和apisecret不应该明文传输，建议只传输apikey，不传输apisecret，用户如需修改直接输入新的就好。
其他信息

Duplicate issue #620: [Feature] 控制台建议【不要明文返回】❌授权凭证密钥
Created: 2025-04-16T11:43:17Z
功能描述 / Description
授权管理列表页面接口

请求动机 / Motivation
以免在不安全的网络环境下造成 凭证泄漏
其他 / Miscellaneous
No response
贡献 / Contribution

 我乐意为此贡献代码！ / I am interested in contributing to this feature!

Closing comment (2025-04-16T12:18:56Z): duplicate #92
Repository: usual2970/certimate

Issue #78: 希望能添加name.com的域名供应商
Created: 2024-09-23T02:58:15Z
希望能添加name.com的域名供应商

Duplicate issue #386: [Feature] 希望增加name.com平台支持
Created: 2024-12-20T08:24:09Z
功能描述
Name.com 是一家经 ICANN 认证的域名注册商和网络托管公司，总部位于科罗拉多州丹佛市。自 2003 年成立以来，该公司已发展成为世界领先的域名注册商之一，可提供近 600 个顶级域名。Name.com 在其网站上提供广泛的产品和服务，帮助个人和企业建立并维护成功的在线形象。该公司销售 DNS 域名、虚拟主机、电子邮件服务、SSL 证书和其他网站产品。
动机
增加多平台支持，有助于增加项目兼容性。
替代方案
无
其他信息
https://www.name.com/

Closing comment (2024-12-20T09:06:36Z): duplicate #78
Repository: usual2970/certimate

Issue #91: [Feature] 请求添加自助上传证书并发布的功能.
Created: 2024-09-24T06:27:58Z
功能描述
当前 Certimate 是通过各厂商的 AccessKey 来进行自动签发证书并 Deploy 到服务器上的.
是否可以支持自行上传证书的公钥和私钥呢?
动机
目前国内还有不少阿里云 / 腾讯云以外的域名提供商 , 例如美橙互联等.
这些供应商没有提供 AccessKey 来操作域名解析. 不能做到自动签发.
所以还需要手动的方式获得证书文件并进行手动部署.
替代方案
目前尚无其他替代方案 , 只能在监控告警后手动处理. 辛苦作者考虑提供该功能 , 谢谢.
其他信息

Duplicate issue #134: [Feature] 能否增加只有手动设置dns方式的域名申请证书
Created: 2024-10-04T14:46:49Z
功能描述
支持某些情况下，掌握的权限只能手动设置dns，没有dns 服务商的授权信息。比如很早期，公司的域名和空间找的一家网络公司服务的，域名和空间都是万网，现在就是阿里云。域名管理和空间管理给到我们了，但不是阿里的会员身份，是单独的控制面板。
域名管理（可设置dns，但无api方式）：https://dc.aliyun.com/login/loginx
主机管理（可上传一个证书）：https://cp.aliyun.com/login
动机
对于可以手动配置dns，但无dns 服务商的授权信息时也可使用。
替代方案
目前是用acme的命令行方式：https://github.com/acmesh-official/acme.sh?tab=readme-ov-file#9-use-dns-manual-mode
其他信息

Closing comment (2025-01-16T04:28:45Z): duplicate #91 #100
Repository: usual2970/certimate

Issue #451: [Feature] 希望部署站点等参数支持自动获取
Created: 2025-02-12T15:57:43Z
功能描述
CDN或宝塔部署站点支持自动获取，采用多选下拉框的方式（如下图）会更方便，首先通过CDN或宝塔接口获取CDN站点，然后默认默认增加一个通配符的选项如 *.aaa.com
动机
减少站点域名输入错误，方便使用
替代方案
无
其他信息
示例效果如图：

Duplicate issue #633: [Feature] 1Panel 证书更新功能希望能够选择证书
Created: 2025-04-20T14:38:12Z
功能描述 / Description
该证书id在1Panel中无法直接获取

希望能够先调用 /api/v1/websites/ssl/search 列出来证书后手动选择需要更新的证书
请求动机 / Motivation
证书id无法在1panel中直接看到，需要抓包获取

其他 / Miscellaneous
No response
贡献 / Contribution

 我乐意为此贡献代码！ / I am interested in contributing to this feature!

Closing comment (2025-04-21T01:23:39Z): duplicate #451
Repository: usual2970/certimate

Issue #471: [Feature] v0.3.x 通知
Created: 2025-03-01T08:55:05Z
功能描述
简要描述你希望添加的功能和相关问题，1 个 ISSUE 只描述一个功能。
开启通知后，每天都会发送通知，会很烦。
之前已经部署成功过了，是否可以参考部署成功跳过通知。
动机
为什么这个功能对项目有帮助？
替代方案
描述你已经考虑过的替代方案。
参考部署通知

其他信息
在这里添加任何相关的附加信息或截图。

Duplicate issue #526: [Feature] 没有部署成功不希望发送通知
Created: 2025-03-17T04:29:31Z
功能描述
工作流的任务配置为每天检测，然后如果发现还没有到期并且不需要部署的时候，就不要执行发送通知的功能
动机
每天定时检测总会发送一个成功或者失败的通知，太骚扰了
替代方案
无
其他信息

Closing comment (2025-03-17T04:43:00Z): duplicate #471
Repository: usual2970/certimate

Issue #458: [Bug] 向ZeroSSL申请RSA2048证书（xxx.xx;*.xxx.xx）出错
Created: 2025-02-20T02:30:00Z
描述问题
向ZeroSSL申请RSA2048证书（xxx.xx;*.xxx.xx）出错，证书管理中也未出现新证书；切换到Let's Encrypt后成功
日志如下：
开始
[2025-02-20 10:14:10]
进入开始节点
申请
[2025-02-20 10:14:10]
进入申请证书节点
[2025-02-20 10:14:42]
申请成功
[2025-02-20 10:14:42]
certificate: Must be no more than 5000 character(s).
workflow_run
{"time":"2025-02-20T02:14:42Z","level":"ERROR","content":"保存申请记录失败","error":"certificate: Must be no more than 5000 character(s)."}],"error":"certificate: Must be no more than 5000 character(s)."}]
复现步骤
每次启动流程都可以遇到
期望的结果
解决错误，流程正常完成
环境

操作系统:  Oracle Linux Server 8.10, docker 26.1.3
浏览器: Chrome 133.0.6943.126
仓库版本: registry.cn-shanghai.aliyuncs.com/usual2970/certimate:v0.3.0-alpha.
12

Duplicate issue #460: [Bug] 上传证书提示超过5120个字符
Created: 2025-02-20T12:34:08Z
描述问题
上传证书提示超过5120个字符
截图

环境

操作系统: [e.g. Windows, macOS]
浏览器: [e.g. Chrome, Safari]
仓库版本: [e.g. v]

Closing comment (2025-02-20T13:06:39Z): duplicate #458
Repository: usual2970/certimate

Issue #100: 能不能不要accesskeyid和accesskeysecret 自己添加txt记录
Created: 2024-09-26T01:57:44Z
我感觉还是直接添加txt记录更好

Duplicate issue #91: [Feature] 请求添加自助上传证书并发布的功能.
Created: 2024-09-24T06:27:58Z
功能描述
当前 Certimate 是通过各厂商的 AccessKey 来进行自动签发证书并 Deploy 到服务器上的.
是否可以支持自行上传证书的公钥和私钥呢?
动机
目前国内还有不少阿里云 / 腾讯云以外的域名提供商 , 例如美橙互联等.
这些供应商没有提供 AccessKey 来操作域名解析. 不能做到自动签发.
所以还需要手动的方式获得证书文件并进行手动部署.
替代方案
目前尚无其他替代方案 , 只能在监控告警后手动处理. 辛苦作者考虑提供该功能 , 谢谢.
其他信息

Closing comment (2025-01-16T04:32:23Z): duplicate #100
Repository: vanniktech/Emoji

Issue #474: Popup takes up full screen when in adjustPan mode
Created: 2020-10-01T13:03:33Z
Reproduction
With this code
<activity android:name=".CustomViewActivity" android:windowSoftInputMode="stateVisible|adjustPan"/> 
it shows:

Duplicate issue #572: The full screen is abnormal
Created: 2022-04-11T07:10:20Z
when the Application or activity style is fullScreen (android:theme="@android:style/Theme.NoTitleBar.Fullscreen")
or set window.setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN)  in activity, the emoji pop is abnormal
version:0.9.0

Closing comment (2022-04-25T10:06:46Z): duplicate of: #474
Repository: vanniktech/Emoji

Issue #474: Popup takes up full screen when in adjustPan mode
Created: 2020-10-01T13:03:33Z
Reproduction
With this code
<activity android:name=".CustomViewActivity" android:windowSoftInputMode="stateVisible|adjustPan"/> 
it shows:

Duplicate issue #487: size display popup emoji wrong when update version 0.7.0 
Created: 2021-01-28T10:19:38Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library: 0.7.0
Affected devices: all device
Affected versions: : 8.0
the new version upgrades very bad dialog. I don't change anything in the source code and update 0.6.0 -> 0.7.0 I have a bug show full-screen dialog emoji. this bug does not have when downgrading 0.6.0. thanks, the team I hope it fixes the new version continues.

Closing comment (2021-04-20T06:49:35Z): Dupe of #474
Repository: vanniktech/Emoji

Issue #191: Galaxy E7 Duos 3G SM-E700H : On this device the soft keyboard and emoji pop are inflated together.
Created: 2017-08-17T05:05:50Z
I have a Samsung galaxy E7 duos, while testing this library i found that the soft keyboard and emoji pop up are visible together. Is there a way or any workaround to handle this?
Coz its working on all the devices except this one.
I am attaching a screen shot to explain a bit more.

Duplicate issue #308: Emoji Popup Issue
Created: 2018-10-03T08:37:53Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library: ios-emoji 0.5.1
Affected devices: OnePlus 6
Affected versions: Android Pie sdk version 28

Emoji Popup not covering Keyboard completely. Please check screenshot.


Screenshot(s) showing the issue and reprodution steps are appreciated.

Closing comment (2018-10-03T09:55:06Z): Dupe of #191
Repository: vanniktech/Emoji

Issue #467: Emoji Popup Window Not Covering soft keyboard completely
Created: 2020-08-27T19:16:59Z
I have tried everything to make the emoji popup to cover the keyboard but not work. Any help please.

Duplicate issue #494: emoji pop up not fitting in keyboard properly. showing space from bottom.
Created: 2021-04-21T11:54:09Z
version 0.5.1
android Q(POCO X3)

Closing comment (2021-04-21T14:35:06Z): Dupe #467
Repository: vanniktech/Emoji

Issue #183: Error:(24, 13) Failed to resolve: com.vanniktech:emoji-google:0.6.0-SNAPSHOT
Created: 2017-08-03T08:39:40Z
Hi.
I tried to include:
   compile 'com.vanniktech:emoji-google:0.5.1' compile 'com.vanniktech:emoji-google:0.6.0-SNAPSHOT'
But it throws me this error: Error:(24, 13) Failed to resolve: com.vanniktech:emoji-google:0.6.0-SNAPSHOT.
Attach is the error image.

Please advice.
Thank you.

Duplicate issue #187: Failed to resolve com.vanniktech:emoji-google:0.6.0-SNAPSHOT
Created: 2017-08-07T10:25:55Z
Hello,
I want to try in gradle but I got this error. what does mean?

thank you very much

Closing comment (2017-08-07T10:37:43Z): Also dupe #183
Repository: vanniktech/Emoji

Issue #485: EmojiUtils.isOnlyEmojis cannot detect 🗯 ,  🗨,  🕳, ❤, ❣ .... 
Created: 2021-01-19T01:14:56Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library:  0.7.0
Affected devices: Any
Affected versions: Any

To replicate issue :
EmojiUtils.isOnlyEmojis("🗯")  // false
EmojiUtils.isOnlyEmojis("🗨")  // false
EmojiUtils.isOnlyEmojis("🕳")  // false
EmojiUtils.isOnlyEmojis("❤")  // false
EmojiUtils.isOnlyEmojis("❣")  // false

this happens to all emojis with 2 codepoints like this:
new GoogleEmoji(new int[] { 0x1F5E8, 0xFE0F }, new String[]{"left_speech_bubble"}, 30, 26, false), new GoogleEmoji(new int[] { 0x1F5EF, 0xFE0F }, new String[]{"right_anger_bubble"}, 30, 27, false),

Duplicate issue #484: Incorrect heart emoji detection in EmojiUtils
Created: 2020-12-17T20:28:01Z
Version of the library: 0.7.0
Affected devices: OnePlus 3
Affected versions: Android 8.0


Hello, some strange behaviour:
EmojiUtils.emojisCount("❤") return 0.
Heart symbol is also ignored in method EmojiUtils.emojis (empty list returned).
Thats all, thank you for time spend on maintaing library :)

Closing comment (2021-04-20T06:45:08Z): Dupe of #485
Repository: vanniktech/Emoji

Issue #176: failed to resolve 
Created: 2017-07-15T22:09:24Z
Failed to resolve: com.vanniktech:emoji-one:0.6.0-SNAPSHOT

Duplicate issue #177: Failed to resolve: com.vanniktech:emoji-ios:0.6.0-SNAPSHOT
Created: 2017-07-17T12:43:42Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library:
Affected devices:
Affected versions:

Screenshot(s) showing the issue and reprodution steps are appreciated.

Closing comment (2017-07-17T12:44:27Z): Dupe of #176. either use 0.5.0 or add the maven snapshot url.
Repository: vanniktech/Emoji

Issue #758: When click on emoji button keyboard is open but edit text is not show emoji keyboard is overlap the edit text.
Created: 2022-05-05T12:23:52Z

Duplicate issue #538: Wrong borders at the bottom
Created: 2022-01-03T14:14:14Z
Element Messenger included the Emoji library.
I encountered a bug where the emoji picker has a wrong border at the bottom.

Using a Google Pixel 5 with FlorisBoard Keyboard.

Closing comment (2024-05-17T07:38:05Z): Same as #758
Repository: vanniktech/Emoji

Issue #191: Galaxy E7 Duos 3G SM-E700H : On this device the soft keyboard and emoji pop are inflated together.
Created: 2017-08-17T05:05:50Z
I have a Samsung galaxy E7 duos, while testing this library i found that the soft keyboard and emoji pop up are visible together. Is there a way or any workaround to handle this?
Coz its working on all the devices except this one.
I am attaching a screen shot to explain a bit more.

Duplicate issue #282: Both Emoji KeyBoard and character Keyboard opens at same time 
Created: 2018-05-24T04:25:58Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library:
Affected devices:
Affected versions:

Screenshot(s) showing the issue and reprodution steps are appreciated.

Closing comment (2018-05-25T10:34:08Z): Dupe of #191
Repository: vanniktech/Emoji

Issue #227: Update to the new whatsapp emojis
Created: 2017-12-04T21:13:46Z
Thank you for filing an issue. If this is a bug that you want to report, please take the time to provide some information:

Version of the library:
Affected devices:
Affected versions:

Screenshot(s) showing the issue and reprodution steps are appreciated.

Duplicate issue #245: Update Emojis
Created: 2018-01-26T05:31:22Z
What a nice library.
Anyway I noticed that Emojis are a little older than WhatsApp ones. Is there a way to update all Emojis in this library everytime they're updated in WhatsApp?
Thanks

Closing comment (2018-01-26T15:18:32Z): Dupe of #227.
We rely on the ordering of the emojis from emojione and they haven't fixed theirs yet - joypixels/emojione#523
Repository: vega/lyra

Issue #92: Visual Transform is hard to see.
Created: 2014-02-20T04:41:51Z
From today’s testing session, Jeff and Greg can’t find the "add visual transform” button.
There are some options for solving these:

Can we somehow add them to the left side?
Add icons

My comments might not make much sense right now.  I have to try to make some examples that use those transforms first before understanding these flows.

Duplicate issue #162: Position of visual layout
Created: 2014-02-26T22:36:45Z
I know we’ve discussed about this before.
But if I understand correctly, right now visual layout is attached to the whole pipeline, not just a particular group marks.  I wonder if that’s the case, should it the visual layout property be on the left side then?
(I know that in Vega spec, you can perform these transform in either data pipeline or in marks.)
Please correct me if I’m wrong.

Closing comment (2014-02-27T00:42:34Z): This is a duplicate of #92. Although, behind the scenes, visual transforms get added to data pipelines, I don't think this is how users conceptualize them.

This is something that we went back and forth on pre-CHI and user tests indicated that once people understood what they are, they preferred them on the right, as they related to visual properties moreso than data transformations.

Conversations at Tapestry have indicated the same because you directly wire up visual transforms to visual properties of marks (and so there's a flow down the right hand panel).
Repository: vega/lyra

Issue #66: Dragging fields to rect mark dropzones should always do the same thing
Created: 2014-02-05T08:05:09Z
It's trying to be too smart right now. If I drag a field to height, and then another field to height, I expect it to do the same thing both times.

Duplicate issue #62: Dragging new field to scale does not completely replace old field
Created: 2014-01-30T20:58:47Z
Step to reproduce

In stations dataset
Create text marks
Drag index to y of text marks
Drag dist to y of text marks
The domain of y scale is still index

Closing comment (2014-02-11T22:45:28Z): I think this is probably related to #66. We need to keep better track of defaults -- if a scale/binding was created by default, and not modified by the user, they wholesale replace it.
Repository: vega/lyra

Issue #11: Be able to specify "group by" data transform using dropzones
Created: 2014-01-26T22:57:01Z
We should be able to drag data fields onto the visualization to add a "group by" data transformation. Perhaps dropzones around the current selected layer for vertical/horizontal/layered layouts?

Duplicate issue #43: Group Transform should be able to act as a drop target
Created: 2014-01-30T07:28:57Z
It’s faster than clicking group and move mouse back to field name and drag those back.

Closing comment (2014-02-11T23:13:32Z): Duplicate of #11 Added group by dropzones in facelift.
Repository: vega/lyra

Issue #505: Mark going beyond max axis value
Created: 2020-10-23T19:15:10Z
Expected Behavior
A line graph should not go above the max axis value
Steps to reproduce behavior

chose cars dataset
chose line mark
drag mean_acceleration to y dropzone
drag year to x dropzone
results in a chart with the line graph going above the max axis value

Duplicate issue #489: Year axis range
Created: 2020-09-29T15:48:12Z
I am reporting a bug

Expected Behavior
When year is bound to an axis, it should only span relevant years.
Actual Behavior
The order in which data are bound to the axes can affect the final visualization, so when year is bound first, the axis starts at 0.
Steps to reproduce behavior

use car dataset
select line (or area) mark
bind year to x axis
bind mean horsepower to y axis
--> results in an x axis starting from 0
vs.
car dataset
select line (or area) mark
bind mean horsepower to y axis
bind year to x asix
--> results in an x axis just spanning relevant years

Closing comment (2020-11-14T08:24:15Z): duplicate of #505
Repository: vega/lyra

Issue #235: Data Import UI
Created: 2016-02-15T03:47:43Z
To be truly useful to a broad community of users, Lyra 2 should make it as easy as possible to import data (JSON, CSV, TSV initially). Voyager took some good steps in this direction, and it would be great to extend this further.

 Import example datasets.
 Import from URL.
 Import from filesystem drag/drop or copy/paste (particularly copy/paste of spreadsheet/tabular data).
 Import from Google sheets, Dropbox, gist, etc.
 Enter tabular data

Some thoughts on import:

Users should be able to change inferred data types, but this should likely be a secondary UI concern (e.g., toggling between types by clicking them on field hover in the data table).
Multiple data pipelines may be created from the same data source. This operation should be quick, and should share the backend model to reduce load latency and memory footprint.

Duplicate issue #180: Loading External JSON Data Source via URL just hangs
Created: 2014-06-25T18:04:41Z
I took data/medals.json and created an identical replica called test.json and hosted it off the root webserver directory so that it is accessible at http://localhost/test.json (which I verified). I then went into Lyra and selected "From Source | New Data Source" and gave it a Name, Selected URL and provided the "http://localhost/test.json"  as the URL and selected JSON as the format. I then clicked the "Load" button and it hangs.

Closing comment (2016-02-15T04:45:18Z): Closing old issues as we begin work on Lyra 2. Issues related to data import will now be tracked in #235.
Repository: vega/lyra

Issue #133: Data Table Column Width
Created: 2014-02-23T05:46:34Z
With some data, users can see only one column at a time, it would be great if the column is resizable.

Duplicate issue #21: No way to see full column names in the data table
Created: 2014-01-26T23:09:52Z
There are two possible solutions I think of right now
a) tooltips
b) allow users to resize column

Closing comment (2014-10-22T18:34:12Z): Duplicate of #133.
Repository: vega/lyra

Issue #70: Schema bubble’s mouseover cursor suggest dragging but they are actually not draggable. 
Created: 2014-02-07T22:39:11Z

Duplicate issue #50: Field bubble in a text field is not selectable 
Created: 2014-01-30T15:20:55Z
Unlike Mac’s finder, clicking on text bubble in vde doesn’t select it.
Also, with openhand cursor, people will expect to drag it.

Closing comment (2014-02-11T22:58:01Z): Duplicate of #70?
Repository: vega/lyra

Issue #69: Filter Box should show error to user
Created: 2014-02-07T22:30:44Z
For example, type d.field.startsWith(“U”) in the filter box

Duplicate issue #76: Resizing Canvas throw this error
Created: 2014-02-19T23:46:03Z
Jeff Snyder got this error when resizing canvas.
SyntaxError: Unexpected token = at Function (native)
at Object.expr (http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:4220:12)
at Function.formula.expr (http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:3187:52)
at http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:4658:12
at Array.forEach (native) at vg.parse.transform (http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:4656:16)
at Array.map (native) at Object.vg.parse.dataflow (http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:4159:34)
at http://idl.cs.washington.edu/projects/lyra/app/js/lib/vega-1.3.3.js:4152:37
at Array.forEach (native) 
angular-1.2.10.min.js:84

(anonymous function)angular-1.2.10.min.js:84
(anonymous function)angular-1.2.10.min.js:62
(anonymous function)angular-1.2.10.min.js:113
eangular-1.2.10.min.js:33
(anonymous function)angular-1.2.10.min.js:37A

I can’t reproduce it yet though.

Closing comment (2014-02-20T00:45:51Z): Hmm, that line seems to be related to having some faulty expression (e.g. in the formula or filter, etc.). So this is probably related to #69
Repository: vega/lyra

Issue #18: Rearrange pipeline items
Created: 2014-01-26T23:06:21Z
Drag-and-drop to rearrange pipeline items, like marks/layers.

Duplicate issue #97: Can’t change order in the pipeline.
Created: 2014-02-20T06:35:22Z
People expect to drag pipeline on the left pane.
Of course, this is very low priority.

Closing comment (2014-02-20T06:37:18Z): Duplicate of #18.
Repository: vega/lyra

Issue #15: Click axes on visualization to select them
Created: 2014-01-26T23:03:57Z
Unfortunately, this is a limitation in Vega (axes don't register events). Perhaps we can ping @jheer to add this to Vega. Or, in the worst case, come up with a workaround in the iVis.

Duplicate issue #86: Select Axis
Created: 2014-02-20T04:20:26Z
Right now, we can click marks on the canvas and the clicked mark will be selected on the right pane.
However, we can’t do the same with axis.

Closing comment (2014-02-20T06:20:50Z): Duplicate of #15. Unfortunately a limitation in Vega.
Repository: vega/ts-json-schema-generator

Issue #189: Support for `Required<T>` typescript helper
Created: 2019-08-05T17:40:24Z
export type T = Required<{ a?: string }>;

Actual:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "type": "object"
    }
  }
}

Expected:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "required": ["a"],
      "type": "object"
    }
  }
}

/**
 * Make all properties in T required
 */
type Required<T> = {
    [P in keyof T]-?: T[P];
};

Duplicate issue #1431: [REG 1.0->1.1] Properties not applied from value type
Created: 2022-10-02T17:55:24Z
type UrlTypes = {

  /**
   * @pattern ^https:\/\/.*$
   */
  url: string;
}

interface AllFields {
  field1: string;
  field2: string;
}

type UrlFields = {
  [key in keyof AllFields]?: UrlTypes['url'];
};

export interface Test {
  foo?: UrlFields;
}
Running:
npx ts-json-schema-generator --no-type-check --path schema-test.ts --type Test --validation-keywords patternProperties --out schema-test.json
The output is missing the pattern in v1.1.2. This is the output from v1.0.0, and I'm marking the lines that are missing:
{
  "$ref": "#/definitions/Test",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "Test": {
      "additionalProperties": false,
      "properties": {
        "foo": {
          "additionalProperties": false,
          "properties": {
            "field1": {
              "pattern": "^https:\\/\\/.*$", // <---------- This is missing
              "type": "string"
            },
            "field2": {
              "pattern": "^https:\\/\\/.*$", // <---------- This is missing
              "type": "string"
            }
          },
          "type": "object"
        }
      },
      "type": "object"
    }
  }
}

Closing comment (2024-05-29T02:48:50Z): Duplicate of #189
Will work again once:
type UrlFields = {
  [key in keyof AllFields]?: UrlTypes['url'];
//                        ~
};
gets fixed
Repository: vega/ts-json-schema-generator

Issue #71: Support Exclude
Created: 2019-02-13T13:49:07Z
Error:
UnknownNodeError: Unknown node "Exclude<ParameterType, ParameterType.Enum | ParameterType.Number>" (ts.SyntaxKind = 175)

Code:
enum ParameterType {
    Enum = "enum",
    Number = "number",
    String = "string",
    Date = "date"
    //...
}

interface IParameter {
    type: Exclude<ParameterType, ParameterType.Enum | ParameterType.Number>;
}

Duplicate issue #100: Add support for conditional type nodes
Created: 2019-05-31T11:41:25Z
Because of YousefED/typescript-json-schema#173 I'm currently trying to migrate to ts-json-schema-generator. The first problem I have with the new tool is missing support for conditional type nodes which worked fine with the typescript-json-schema tool. Here is a minimal example:
export type TypeName<T> =
    T extends string ? "string" :
    T extends number ? "number" :
    T extends boolean ? "boolean" :
    "object";

export type TestJSON = TypeName<string>;
When I try to generate the schema for TestJSON with this tool then I get this error message:
UnknownNodeError: Unknown node "TypeName<string>" (ts.SyntaxKind = 176)

I really like the clean structure of the new tool and it looks pretty straight forward how to implement this feature by adding a ConditionalTypeNodeParser class like this:
export class ConditionalTypeNodeParser implements SubNodeParser {
    public constructor(
        private typeChecker: ts.TypeChecker,
        private childNodeParser: NodeParser,
    ) {
    }

    public supportsNode(node: ts. ConditionalTypeNode): boolean {
        return node.kind === ts.SyntaxKind.ConditionalType;
    }

    public createType(node: ts.ConditionalTypeNode, context: Context): BaseType {
        ... magic here ...
    }
}
But unfortunately I lack the skills to implement the createType method. In theory the method has to check if node.checkType is assignable to node.extendsType and then returns node.trueType or node.falseType. But I don't know if this assignability check must be written from scratch here or if TypeScript already exposes some functionality to do this. And it gets more complicated if the check type is a union type so TypeName<string | Date> is resolved to "string" | "object" in this example.

Closing comment (2019-05-31T18:43:49Z): This is closely related to #71
Repository: vega/ts-json-schema-generator

Issue #976: NoRootNamesError: No source files found
Created: 2021-10-06T07:37:20Z
I just updated from version 0.95.0 to 0.96.0 and the schema generator stopped working, I now get this message:
> ts-json-schema-generator -f tsconfig.json -t Foo > foo.schema.json

NoRootNamesError: No source files found

Can be reproduced with a minimal tsconfig.json (even one containing an empty object) and a simple export interface Foo { bar: string } type. Works with schema generator 0.95.0, but not with 0.96.0
Was there a change in the CLI parameters? I can't find any entry in the changelog which sounds like a CLI change.
And maybe this issue is a good point to discuss the versioning of the the schema-generator. I'm using it for a long time now and I would say the interfaces for which I generate JSON schemas are very complex (Lots of generic types with many mapped types and conditional types for example). And since my last contributions to this project two years ago I never had a problem with it (well, until now). So in my opinion the schema generator is very stable and earns the right to get a production version number. After this the versioning should follow the semver paradigm and the major version number should be incremented when the public API (including the CLI parameters) is no longer compatible to the previous version.

Duplicate issue #987: exclude single file from --path ?
Created: 2021-10-15T07:42:56Z
Hello and thank you!
I'd like to do something along the lines of --path 'src/!(app)*.ts' but am not figuring out a negate option.
Any options to include *.ts but leave out app.ts?
Its a different issue, but the reason I need to exclude app.ts is due to:
Error: Unknown node "() => {" (ts.SyntaxKind = 212)
on err in (with our without the explicit type):
  (err: NodeJS.ErrnoException) => {
    if (err) {

Closing comment (2021-10-15T17:42:35Z): aah looks related to #976 and #979
Repository: vega/ts-json-schema-generator

Issue #115: Intersections do not properly merge property types
Created: 2019-06-04T12:24:10Z
When creating an intersection of two types which have the same properties but with different types these types are not properly merged.
Example:
interface A {
  x: boolean;
}

interface B {
  x: true;
}

export type C = A & B;
The generated schema now must only allow trueas value for x but instead it also allows false because it simply required a boolean. It works when swapping the type to B & A. Looks like the left type always wins when both types define the same property.
Another example:
interface A {
  x: { a: number; };
}

interface B {
  x: { b: number; };
}

export type C = A & B;
The generated schema now only allows the property a under x but it must also allow b. Swapping the type to B & A doesn't help in this case because then only b is allowed.

Duplicate issue #58: Incorrect output for intersection type 
Created: 2019-01-01T07:38:09Z
In Vega-Lite, MarkPropFieldDef's bin property should not support "binned" as its value.  However, the generated JSON schema includes "binned".

Closing comment (2019-06-26T07:08:38Z): Maybe someone familiar with Vega can do this "simplification" and post the simplified test case here so people unrelated to vega can try to help? I tried and gave up after following dozens of other types... Mabye this bug is the same as #115 I reported a few weeks ago but I can't be sure without a proper bug description.
Repository: vega/ts-json-schema-generator

Issue #189: Support for `Required<T>` typescript helper
Created: 2019-08-05T17:40:24Z
export type T = Required<{ a?: string }>;

Actual:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "type": "object"
    }
  }
}

Expected:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "required": ["a"],
      "type": "object"
    }
  }
}

/**
 * Make all properties in T required
 */
type Required<T> = {
    [P in keyof T]-?: T[P];
};

Duplicate issue #993: Support for `Pick`, `Exclude` and `Omit` typescript type helpers.
Created: 2021-10-20T22:28:25Z
Hi,
I have the following example which seems to return erroneous results:
export type A = {
	readonly a1: string
	readonly a2: string
}

export type B1 = A & {
	readonly b1: string
}

export type B2 = A & {
	readonly b2: string
}

export type B = B1 | B2

export type C = Omit<B, 'a2'> 
The JSON schema for type C should be a type union, but is not:
$ yarn run --silent ts-json-schema-generator --path test.ts --type C
{
  "$ref": "#/definitions/C",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "C": {
      "additionalProperties": false,
      "properties": {
        "a1": {
          "type": "string"
        },
        "b1": {
          "type": "string"
        },
        "b2": {
          "type": "string"
        }
      },
      "required": [
        "a1",
        "b1",
        "b2"
      ],
      "type": "object"
    }
  }
}
Note that the type B seems to be correctly handled:
$ yarn run --silent ts-json-schema-generator --path A.ts --type B   
{
  "$ref": "#/definitions/B",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "B": {
      "anyOf": [
        {
          "$ref": "#/definitions/B1"
        },
        {
          "$ref": "#/definitions/B2"
        }
      ]
    },
    "B1": {
      "additionalProperties": false,
      "properties": {
        "a1": {
          "type": "string"
        },
        "a2": {
          "type": "string"
        },
        "b1": {
          "type": "string"
        }
      },
      "required": [
        "a1",
        "a2",
        "b1"
      ],
      "type": "object"
    },
    "B2": {
      "additionalProperties": false,
      "properties": {
        "a1": {
          "type": "string"
        },
        "a2": {
          "type": "string"
        },
        "b2": {
          "type": "string"
        }
      },
      "required": [
        "a1",
        "a2",
        "b2"
      ],
      "type": "object"
    }
  }
}
Note that I am running "ts-json-schema-generator": "0.96.0" and "typescript": "4.3.5".

Closing comment (2024-05-29T02:30:51Z): Probably also related to #189
Repository: vega/ts-json-schema-generator

Issue #171: Enums not supported for index signatures
Created: 2019-07-22T11:19:10Z
Using an enum as an index signature is not supported. For example:
enum Test {
    A = 'a',
    B = 'b',
    C = 'c'
}

export type MyObject = {
    [P in Test]: string;
};
is valid TS but throw the following error:
Unexpected key type "enum-1537915844-0-51-1537915844-0-106" for type "{
        [P in Test]: string;
    }" (expected "UnionType" or "StringType")

See repro: #170

Duplicate issue #566: Unexpected type for enum
Created: 2020-11-17T20:02:17Z
Not exactly sure why this is erroring...but I assume it has something to do with the generics:
test.ts
enum Module {
  A = 'A',
  B = 'B',
}

interface AOptions {
  name: string;
  quantity: number;
}

interface BOptions {
  name: string;
  color: string;
}

interface OptionsMap {
  [Module.A]: Pick<AOptions, 'quantity'>;
  [Module.B]: Pick<BOptions, 'color'>;
}

type Options<T = Module> = T extends Module ? OptionsMap[T] : null;

export interface Store {
  options: Options;
}

command
npx ts-json-schema-generator --path ./test.ts --type "Store"

Closing comment (2020-11-17T20:07:26Z): https://github.com/vega/ts-json-schema-generator/blob/master/src/NodeParser/IndexedAccessTypeNodeParser.ts
Looks like there's an issue with this...so it's similar to #171 #170
Repository: vega/ts-json-schema-generator

Issue #98: Get json schema of parameters from a function
Created: 2019-05-26T09:30:34Z
Would it be possible to get the JSON schema for the parameters of a function (or a method)?
For example:
export interface GetListInput {
    foo: string;
}

export function getList(input: GetListInput, input2: string) {
    // some code
}
I would get something like array:
{
  "$ref": "#/definitions/params",
  "$schema": "http://json-schema.org/draft-06/schema#",
  "definitions": {
    "GetListInput": {
      "additionalProperties": false,
      "properties": {
        "foo": {
          "type": "string"
        }
      },
      "required": [
        "foo"
      ],
      "type": "object"
    },
    "params": {
      "items": [
        {
          "$ref": "#/definitions/GetListInput"
        },
        {
          "type": "string"
        }
      ],
      "maxItems": 2,
      "minItems": 2,
      "type": "array"
    }
  }

Duplicate issue #470: Interfaces methods mapping in a json schema
Created: 2020-07-24T14:45:13Z
Is there a way to define methods of an interface inside a json schema ?
for example
export interface A {
   prop1: string;
   method1(param1: string): string;
}

only generates
{
    "A": {
      "type": "object",
      "properties": {
        "prop1": {
          "type": "string"
        }
    }
}

Is there a valid json schema way to provide something like this ?
{
  "IApi": {
    "type": "object",
    "properties": {
      "prop1": {
        "type": "string"
      },
      "methods": {
        "method1": {
          "type": "object",
          "properties": {
            "parameters": {
              "type": "array",
              "items": {
                ...
              }
            },
            "return": {
              "type": ...
            }
          }
        }
      }
    }
  }
}

I try to model methods in the standard of schema, but didn't know if it is possible

Closing comment (2020-07-24T14:55:43Z): Duplicate of #98
Repository: vega/ts-json-schema-generator

Issue #189: Support for `Required<T>` typescript helper
Created: 2019-08-05T17:40:24Z
export type T = Required<{ a?: string }>;

Actual:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "type": "object"
    }
  }
}

Expected:
{
  "$ref": "#/definitions/T",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "T": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        }
      },
      "required": ["a"],
      "type": "object"
    }
  }
}

/**
 * Make all properties in T required
 */
type Required<T> = {
    [P in keyof T]-?: T[P];
};

Duplicate issue #1980: Required types not allowed
Created: 2024-05-29T21:16:42Z
Hi 👋 all !
We have two type cases where the JSON schema output seems to be not good:
export type ReqAll<T> = Required<
  {
    [P in keyof T]: ReqAll<T[P]>;
  }
>;

export type WithReq<T, K extends keyof T> = T & { [P in K]-?: T[P] };

export type Ab = { a?: string; b?: boolean };

export type Ra = {
  ra: ReqAll<Ab>;
  wr: WithReq<Ab, 'a'>;
};

The generated schema for Ra type is:
{
  "$ref": "#/definitions/Ra",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "Ra": {
      "additionalProperties": false,
      "properties": {
        "ra": {
          "$ref": "#/definitions/ReqAll%3CAb%3E"
        },
        "wr": {
          "$ref": "#/definitions/WithReq%3CAb%2C%22a%22%3E"
        }
      },
      "required": [
        "ra",
        "wr"
      ],
      "type": "object"
    },
    "ReqAll<(boolean|undefined)>": {
      "additionalProperties": false,
      "type": "object"
    },
    "ReqAll<(string|undefined)>": {
      "additionalProperties": false,
      "type": "object"
    },
    "ReqAll<Ab>": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "$ref": "#/definitions/ReqAll%3C(string%7Cundefined)%3E"
        },
        "b": {
          "$ref": "#/definitions/ReqAll%3C(boolean%7Cundefined)%3E"
        }
      },
      "type": "object"
    },
    "WithReq<Ab,\"a\">": {
      "additionalProperties": false,
      "properties": {
        "a": {
          "type": "string"
        },
        "b": {
          "type": "boolean"
        }
      },
      "type": "object"
    }
  }
}

Would you mind to help us with this case? Is there any workaround?
Many thanks!

Closing comment (2024-05-29T21:24:24Z): Duplicate of #189
Repository: vega/vega-lite

Issue #90: Axes Options for Small Multiples
Created: 2014-12-28T15:14:53Z
Right now we only show axes for small multiples once per axes in a separate group.
Maybe some users want to show axes in every single cell

Duplicate issue #920: Draw x,y grid inside facet
Created: 2016-01-11T23:33:11Z
Current faceted charts have shared grid across multiple like this:

However, having separate grid for different singles like an example below is nicer.

——
TODO

 add a property for split axis mode (Need to think what should be the name though)

In this mode

 hide grid from the outside shared x/y axis
 add inner x/y axis (inside each cell group) that shows only grid
 decide which properties get applied to the outer axis (e.g., ticks)

Closing comment (2016-01-12T19:45:38Z): Related to #90